summary refs log tree commit diff
path: root/Documentation/kbuild
diff options
context:
space:
mode:
authorBaruch Siach <baruch@tkos.co.il>2022-07-14 07:25:46 +0300
committerMasahiro Yamada <masahiroy@kernel.org>2022-07-27 21:18:00 +0900
commit59316eac0e5ba5863594a793f6d8b5d8ccb8e880 (patch)
treebddbae3cc75d050909832264b06fda09204bd692 /Documentation/kbuild
parentaac289653fa5adf9e9985e4912c1d24a3e8cbab2 (diff)
downloadlinux-59316eac0e5ba5863594a793f6d8b5d8ccb8e880.tar.gz
docs: kbuild: fix typo
on -> one.

Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'Documentation/kbuild')
-rw-r--r--Documentation/kbuild/kconfig-language.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/kbuild/kconfig-language.rst b/Documentation/kbuild/kconfig-language.rst
index a7173843a294..7fb398649f51 100644
--- a/Documentation/kbuild/kconfig-language.rst
+++ b/Documentation/kbuild/kconfig-language.rst
@@ -672,7 +672,7 @@ Future kconfig work
 Work on kconfig is welcomed on both areas of clarifying semantics and on
 evaluating the use of a full SAT solver for it. A full SAT solver can be
 desirable to enable more complex dependency mappings and / or queries,
-for instance on possible use case for a SAT solver could be that of handling
+for instance one possible use case for a SAT solver could be that of handling
 the current known recursive dependency issues. It is not known if this would
 address such issues but such evaluation is desirable. If support for a full SAT
 solver proves too complex or that it cannot address recursive dependency issues