Kconfig: Use a short, consistent style for prompts
Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
This commit is contained in:
parent
bb0b66e15a
commit
8cf8db3a73
127 changed files with 629 additions and 1258 deletions
|
@ -9,23 +9,20 @@ source "lib/libc/Kconfig"
|
|||
menu "Additional libraries"
|
||||
|
||||
config JSON_LIBRARY
|
||||
bool
|
||||
prompt "Build JSON library"
|
||||
bool "Build JSON library"
|
||||
help
|
||||
Build a minimal JSON parsing/encoding library. Used by sample
|
||||
applications such as the NATS client.
|
||||
|
||||
config RING_BUFFER
|
||||
bool
|
||||
prompt "Enable ring buffers"
|
||||
bool "Enable ring buffers"
|
||||
help
|
||||
Enable usage of ring buffers. This is similar to kernel FIFOs but ring
|
||||
buffers manage their own buffer memory and can store arbitrary data.
|
||||
For optimal performance, use buffer sizes that are a power of 2.
|
||||
|
||||
config BASE64
|
||||
bool
|
||||
prompt "Enable base64 encoding and decoding"
|
||||
bool "Enable base64 encoding and decoding"
|
||||
help
|
||||
Enable base64 encoding and decoding functionality
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue