I'm not very happy with hint #2. I struggled with ways to express it
and finally decided to ship it^W^W release early/release often. :)
From: Randy Dunlap <firstname.lastname@example.org>
Add a section on kconfig hints: how to do <something> in Kconfig files.
Fix a few typos/spellos.
Signed-off-by: Randy Dunlap <email@example.com>
Documentation/kbuild/kconfig-language.txt | 54 ++++++++++++++++++++---
1 file changed, 48 insertions(+), 6 deletions(-)
@@ -24,7 +24,7 @@ visible if its parent entry is also visi
-Most entries define a config option, all other entries help to organize
+Most entries define a config option; all other entries help to organize
them. A single configuration option is defined like this:
@@ -50,7 +50,7 @@ applicable everywhere (see syntax).
- type definition: "bool"/"tristate"/"string"/"hex"/"int"
Every config option must have a type. There are only two basic types:
- tristate and string, the other types are based on these two. The type
+ tristate and string; the other types are based on these two. The type
definition optionally accepts an input prompt, so these two examples
@@ -108,7 +108,7 @@ applicable everywhere (see syntax).
equal to 'y' without visiting the dependencies. So abusing
select you are able to select a symbol FOO even if FOO depends
on BAR that is not set. In general use select only for
- non-visible symbols (no promts anywhere) and for symbols with
+ non-visible symbols (no prompts anywhere) and for symbols with
no dependencies. That will limit the usefulness but on the
other hand avoid the illegal configurations all over. kconfig
should one day warn about such things.
@@ -162,9 +162,9 @@ An expression can have a value of 'n', '
respectively for ...