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:
Ulf Magnusson 2018-08-14 16:19:20 +02:00 committed by Anas Nashif
commit 8cf8db3a73
127 changed files with 629 additions and 1258 deletions

View file

@ -7,8 +7,7 @@
#
menuconfig DHT
bool
prompt "DHT Temperature and Humidity Sensor"
bool "DHT Temperature and Humidity Sensor"
depends on GPIO
help
Enable driver for the DHT temperature and humidity sensor family.
@ -21,22 +20,19 @@ choice
Choose desired chip type from the DHT family.
config DHT_CHIP_DHT11
bool
prompt "DHT11"
bool "DHT11"
help
Choose this option to enable the DHT11 chip.
config DHT_CHIP_DHT22
bool
prompt "DHT22"
bool "DHT22"
help
Choose this option to enable the DHT22 chip.
endchoice
config DHT_NAME
string
prompt "Driver name"
string "Driver name"
default "DHT11" if DHT_CHIP_DHT11
default "DHT22" if DHT_CHIP_DHT22
depends on DHT
@ -44,8 +40,7 @@ config DHT_NAME
Device name with which the sensor is identified.
config DHT_GPIO_DEV_NAME
string
prompt "GPIO device"
string "GPIO device"
default "GPIO_0"
depends on DHT
help
@ -53,8 +48,7 @@ config DHT_GPIO_DEV_NAME
is connected.
config DHT_GPIO_PIN_NUM
int
prompt "Interrupt GPIO pin number"
int "Interrupt GPIO pin number"
default 0
depends on DHT
help