kevin/linux
1
Fork 0
Code

Documentation: kconfig: explicitly document missing prompt

Browse Source 
There are a few lines in the kbuild-language.rst document which
obliquely reference the behavior of config options without prompts.
But there is nothing in the obvious location that explicitly calls
out that users cannot edit config options unless they have a prompt.

Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
This commit is contained in:
Stephen Brennan 2024-08-23 12:41:51 -07:00 committed by Masahiro Yamada
parent 87af9388b4
commit d97eae80d5
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/kbuild/kconfig-language.rst
View File

@ -70,7 +70,11 @@ applicable everywhere (see syntax).
Every menu entry can have at most one prompt, which is used to display Every menu entry can have at most one prompt, which is used to display
to the user. Optionally dependencies only for this prompt can be added to the user. Optionally dependencies only for this prompt can be added
with "if". with "if". If a prompt is not present, the config option is a non-visible
symbol, meaning its value cannot be directly changed by the user (such as
altering the value in ``.config``) and the option will not appear in any
config menus. Its value can only be set via "default" and "select" (see
below).
- default value: "default" <expr> ["if" <expr>] - default value: "default" <expr> ["if" <expr>]