Kconfig: Great White Handkerchief going round
Subsystems (245)
Behold, Jatravartids! The Great White Handkerchief is coming to massacres many thousands of irregular whitespaces and tabs that stepped too far out of line. It's first defenseless victims are the Kconfig files ...
--mtx
PATCH 1/114 drivers: gpio: Kconfig: pedantic formatting
Formatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/gpio/Kconfig | 50 +++++++++++++++++++++++++------------------------- 1 file changed, 25 insertions(+), 25 deletions(-)
drivers/gpio/Kconfig +25 -25
@@ -27,12 +27,12 @@ config GPIOLIB_FASTPATH_LIMIT range 32 512 default 512 help - This adjusts the point at which certain APIs will switch from - using a stack allocated buffer to a dynamically allocated buffer. + This adjusts the point at which certain APIs will switch from + using a stack allocated buffer to a dynamically allocated buffer. - You shouldn't need to change this unless you really need to - optimize either stack space or performance. Change this carefully - since setting an incorrect value could cause stack corruption. + You shouldn't need to change this unless you really need to + optimize either stack space or performance. Change this carefully + since setting an incorrect value could cause stack corruption. config OF_GPIO def_bool y
@@ -320,7 +320,7 @@ config GPIO_MENZ127 depends on MCB select GPIO_GENERIC help - Say yes here to support the MEN 16Z127 GPIO Controller + Say yes here to support the MEN 16Z127 GPIO Controller config GPIO_MM_LANTIQ bool "Lantiq Memory mapped GPIOs"
@@ -862,11 +862,11 @@ config GPIO_MAX732X Input and Output (designed by 'P'). The combinations are listed below: - 8 bits: max7319 (8I), max7320 (8O), max7321 (8P), - max7322 (4I4O), max7323 (4P4O) + 8 bits: max7319 (8I), max7320 (8O), max7321 (8P), + max7322 (4I4O), max7323 (4P4O) - 16 bits: max7324 (8I8O), max7325 (8P8O), - max7326 (4I12O), max7327 (4P12O) + 16 bits: max7324 (8I8O), max7325 (8P8O), + max7326 (4I12O), max7327 (4P12O) Board setup code must specify the model to use, and the start number for these GPIOs.
@@ -893,17 +893,17 @@ config GPIO_PCA953X SMBus I/O expanders, made mostly by NXP or TI. Compatible models include: - 4 bits: pca9536, pca9537 + 4 bits: pca9536, pca9537 - 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554, - pca9556, pca9557, pca9574, tca6408, tca9554, xra1202 + 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554, + pca9556, pca9557, pca9574, tca6408, tca9554, xra1202 - 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575, - tca6416 + 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575, + tca6416 - 24 bits: tca6424 + 24 bits: tca6424 - 40 bits: pca9505, pca9698 + 40 bits: pca9505, pca9698 config GPIO_PCA953X_IRQ bool "Interrupt controller support for PCA953x"
@@ -925,7 +925,7 @@ config GPIO_PCF857X 8 bits: pcf8574, pcf8574a, pca8574, pca8574a, pca9670, pca9672, pca9674, pca9674a, - max7328, max7329 + max7328, max7329 16 bits: pcf8575, pcf8575c, pca8575, pca9671, pca9673, pca9675
@@ -1047,9 +1047,9 @@ config HTC_EGPIO bool "HTC EGPIO support" depends on GPIOLIB && ARM help - This driver supports the CPLD egpio chip present on - several HTC phones. It provides basic support for input - pins, output pins, and irqs. + This driver supports the CPLD egpio chip present on + several HTC phones. It provides basic support for input + pins, output pins, and irqs. config GPIO_JANZ_TTL tristate "Janz VMOD-TTL Digital IO Module"
@@ -1085,7 +1085,7 @@ config GPIO_LP873X on LP873X PMICs. This driver can also be built as a module. If so, the module will be - called gpio-lp873x. + called gpio-lp873x. config GPIO_LP87565 tristate "TI LP87565 GPIO"
@@ -1436,9 +1436,9 @@ config GPIO_VIPERBOARD Say yes here to access the GPIO signals of Nano River Technologies Viperboard. There are two GPIO chips on the board: gpioa and gpiob. - See viperboard API specification and Nano - River Tech's viperboard.h for detailed meaning - of the module parameters. + See viperboard API specification and Nano + River Tech's viperboard.h for detailed meaning + of the module parameters. endmenu
Signature · 1 line
1.9.1
PATCH 2/114 drivers: iio: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/iio/Kconfig | 24 +-- drivers/iio/accel/Kconfig | 48 +++--- drivers/iio/adc/Kconfig | 20 +-- drivers/iio/chemical/Kconfig | 12 +- drivers/iio/common/ms_sensors/Kconfig | 2 +- drivers/iio/humidity/Kconfig | 20 +-- drivers/iio/light/Kconfig | 274 +++++++++++++++++----------------- drivers/iio/potentiometer/Kconfig | 34 ++--- drivers/iio/temperature/Kconfig | 16 +- 9 files changed, 225 insertions(+), 225 deletions(-)
drivers/iio/Kconfig +12 -12
@@ -39,28 +39,28 @@ config IIO_TRIGGER data now' interrupt. config IIO_CONSUMERS_PER_TRIGGER - int "Maximum number of consumers per trigger" - depends on IIO_TRIGGER - default "2" - help - This value controls the maximum number of consumers that a - given trigger may handle. Default is 2. + int "Maximum number of consumers per trigger" + depends on IIO_TRIGGER + default "2" + help + This value controls the maximum number of consumers that a + given trigger may handle. Default is 2. config IIO_SW_DEVICE tristate "Enable software IIO device support" select IIO_CONFIGFS help - Provides IIO core support for software devices. A software - device can be created via configfs or directly by a driver - using the API provided. + Provides IIO core support for software devices. A software + device can be created via configfs or directly by a driver + using the API provided. config IIO_SW_TRIGGER tristate "Enable software triggers support" select IIO_CONFIGFS help - Provides IIO core support for software triggers. A software - trigger can be created via configfs or directly by a driver - using the API provided. + Provides IIO core support for software triggers. A software + trigger can be created via configfs or directly by a driver + using the API provided. config IIO_TRIGGERED_EVENT tristate
drivers/iio/accel/Kconfig +24 -24
68 lines not on this page · raw message
drivers/iio/adc/Kconfig +10 -10
@@ -390,7 +390,7 @@ config HX711 This driver uses two GPIOs, one acts as the clock and controls the channel selection and gain, the other one is used for the measurement - data + data Currently the raw value is read from the chip and delivered. To get an actual weight one needs to subtract the
@@ -585,17 +585,17 @@ config MCP3911 called mcp3911. config MEDIATEK_MT6577_AUXADC - tristate "MediaTek AUXADC driver" - depends on ARCH_MEDIATEK || COMPILE_TEST - depends on HAS_IOMEM - help - Say yes here to enable support for MediaTek mt65xx AUXADC. + tristate "MediaTek AUXADC driver" + depends on ARCH_MEDIATEK || COMPILE_TEST + depends on HAS_IOMEM + help + Say yes here to enable support for MediaTek mt65xx AUXADC. - The driver supports immediate mode operation to read from one of sixteen - channels (external or internal). + The driver supports immediate mode operation to read from one of sixteen + channels (external or internal). - This driver can also be built as a module. If so, the module will be - called mt6577_auxadc. + This driver can also be built as a module. If so, the module will be + called mt6577_auxadc. config MEN_Z188_ADC tristate "MEN 16z188 ADC IP Core support"
drivers/iio/chemical/Kconfig +6 -6
@@ -12,14 +12,14 @@ config ATLAS_PH_SENSOR select IIO_TRIGGERED_BUFFER select IRQ_WORK help - Say Y here to build I2C interface support for the following - Atlas Scientific OEM SM sensors: + Say Y here to build I2C interface support for the following + Atlas Scientific OEM SM sensors: * pH SM sensor * EC SM sensor * ORP SM sensor - To compile this driver as module, choose M here: the - module will be called atlas-ph-sensor. + To compile this driver as module, choose M here: the + module will be called atlas-ph-sensor. config BME680 tristate "Bosch Sensortec BME680 sensor driver"
@@ -47,8 +47,8 @@ config BME680_SPI config CCS811 tristate "AMS CCS811 VOC sensor" depends on I2C - select IIO_BUFFER - select IIO_TRIGGERED_BUFFER + select IIO_BUFFER + select IIO_TRIGGERED_BUFFER help Say Y here to build I2C interface support for the AMS CCS811 VOC (Volatile Organic Compounds) sensor
drivers/iio/common/ms_sensors/Kconfig +1 -1
@@ -3,4 +3,4 @@ # config IIO_MS_SENSORS_I2C - tristate + tristate
drivers/iio/humidity/Kconfig +10 -10
@@ -4,16 +4,16 @@ menu "Humidity sensors" config AM2315 - tristate "Aosong AM2315 relative humidity and temperature sensor" - depends on I2C - select IIO_BUFFER - select IIO_TRIGGERED_BUFFER - help - If you say yes here you get support for the Aosong AM2315 - relative humidity and ambient temperature sensor. + tristate "Aosong AM2315 relative humidity and temperature sensor" + depends on I2C + select IIO_BUFFER + select IIO_TRIGGERED_BUFFER + help + If you say yes here you get support for the Aosong AM2315 + relative humidity and ambient temperature sensor. - This driver can also be built as a module. If so, the module will - be called am2315. + This driver can also be built as a module. If so, the module will + be called am2315. config DHT11 tristate "DHT11 (and compatible sensors) driver"
@@ -78,7 +78,7 @@ config HTS221_SPI config HTU21 tristate "Measurement Specialties HTU21 humidity & temperature sensor" depends on I2C - select IIO_MS_SENSORS_I2C + select IIO_MS_SENSORS_I2C help If you say yes here you get support for the Measurement Specialties HTU21 humidity and temperature sensor.
drivers/iio/light/Kconfig +137 -137
475 lines not on this page · raw message
drivers/iio/potentiometer/Kconfig +17 -17
@@ -26,26 +26,26 @@ config DS1803 module will be called ds1803. config MAX5481 - tristate "Maxim MAX5481-MAX5484 Digital Potentiometer driver" - depends on SPI - help - Say yes here to build support for the Maxim - MAX5481, MAX5482, MAX5483, MAX5484 digital potentiometer - chips. + tristate "Maxim MAX5481-MAX5484 Digital Potentiometer driver" + depends on SPI + help + Say yes here to build support for the Maxim + MAX5481, MAX5482, MAX5483, MAX5484 digital potentiometer + chips. - To compile this driver as a module, choose M here: the - module will be called max5481. + To compile this driver as a module, choose M here: the + module will be called max5481. config MAX5487 - tristate "Maxim MAX5487/MAX5488/MAX5489 Digital Potentiometer driver" - depends on SPI - help - Say yes here to build support for the Maxim - MAX5487, MAX5488, MAX5489 digital potentiometer - chips. - - To compile this driver as a module, choose M here: the - module will be called max5487. + tristate "Maxim MAX5487/MAX5488/MAX5489 Digital Potentiometer driver" + depends on SPI + help + Say yes here to build support for the Maxim + MAX5487, MAX5488, MAX5489 digital potentiometer + chips. + + To compile this driver as a module, choose M here: the + module will be called max5487. config MCP4018 tristate "Microchip MCP4017/18/19 Digital Potentiometer driver"
drivers/iio/temperature/Kconfig +8 -8
@@ -66,14 +66,14 @@ config TMP006 be called tmp006. config TMP007 - tristate "TMP007 infrared thermopile sensor with Integrated Math Engine" - depends on I2C - help - If you say yes here you get support for the Texas Instruments - TMP007 infrared thermopile sensor with Integrated Math Engine. - - This driver can also be built as a module. If so, the module will - be called tmp007. + tristate "TMP007 infrared thermopile sensor with Integrated Math Engine" + depends on I2C + help + If you say yes here you get support for the Texas Instruments + TMP007 infrared thermopile sensor with Integrated Math Engine. + + This driver can also be built as a module. If so, the module will + be called tmp007. config TSYS01 tristate "Measurement Specialties TSYS01 temperature sensor using I2C bus connection"
Signature · 1 line
1.9.1
PATCH 3/114 drivers: input: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/input/keyboard/Kconfig | 16 ++++++++-------- drivers/input/misc/Kconfig | 26 +++++++++++++------------- drivers/input/mouse/Kconfig | 26 +++++++++++++------------- drivers/input/serio/Kconfig | 2 +- drivers/input/tablet/Kconfig | 20 ++++++++++---------- drivers/input/touchscreen/Kconfig | 2 +- 6 files changed, 46 insertions(+), 46 deletions(-)
drivers/input/keyboard/Kconfig +8 -8
@@ -138,14 +138,14 @@ config KEYBOARD_ATKBD_RDI_KEYCODES left-hand column. config KEYBOARD_QT1070 - tristate "Atmel AT42QT1070 Touch Sensor Chip" - depends on I2C - help - Say Y here if you want to use Atmel AT42QT1070 QTouch - Sensor chip as input device. - - To compile this driver as a module, choose M here: - the module will be called qt1070 + tristate "Atmel AT42QT1070 Touch Sensor Chip" + depends on I2C + help + Say Y here if you want to use Atmel AT42QT1070 QTouch + Sensor chip as input device. + + To compile this driver as a module, choose M here: + the module will be called qt1070 config KEYBOARD_QT2160 tristate "Atmel AT42QT2160 Touch Sensor Chip"
drivers/input/misc/Kconfig +13 -13
@@ -240,13 +240,13 @@ config INPUT_APANEL select INPUT_POLLDEV select CHECK_SIGNATURE help - Say Y here for support of the Application Panel buttons, used on - Fujitsu Lifebook. These are attached to the mainboard through - an SMBus interface managed by the I2C Intel ICH (i801) driver, - which you should also build for this kernel. + Say Y here for support of the Application Panel buttons, used on + Fujitsu Lifebook. These are attached to the mainboard through + an SMBus interface managed by the I2C Intel ICH (i801) driver, + which you should also build for this kernel. - To compile this driver as a module, choose M here: the module will - be called apanel. + To compile this driver as a module, choose M here: the module will + be called apanel. config INPUT_GP2A tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
@@ -273,12 +273,12 @@ config INPUT_GPIO_DECODER depends on GPIOLIB || COMPILE_TEST select INPUT_POLLDEV help - Say Y here if you want driver to read status of multiple GPIO - lines and report the encoded value as an absolute integer to - input subsystem. + Say Y here if you want driver to read status of multiple GPIO + lines and report the encoded value as an absolute integer to + input subsystem. - To compile this driver as a module, choose M here: the module - will be called gpio_decoder. + To compile this driver as a module, choose M here: the module + will be called gpio_decoder. config INPUT_IXP4XX_BEEPER tristate "IXP4XX Beeper support"
@@ -543,8 +543,8 @@ config INPUT_PCF50633_PMU tristate "PCF50633 PMU events" depends on MFD_PCF50633 help - Say Y to include support for delivering PMU events via input - layer on NXP PCF50633. + Say Y to include support for delivering PMU events via input + layer on NXP PCF50633. config INPUT_PCF8574 tristate "PCF8574 Keypad input device"
drivers/input/mouse/Kconfig +13 -13
@@ -91,14 +91,14 @@ config MOUSE_PS2_SYNAPTICS_SMBUS If unsure, say Y. config MOUSE_PS2_CYPRESS - bool "Cypress PS/2 mouse protocol extension" if EXPERT - default y - depends on MOUSE_PS2 - help - Say Y here if you have a Cypress PS/2 Trackpad connected to - your system. + bool "Cypress PS/2 mouse protocol extension" if EXPERT + default y + depends on MOUSE_PS2 + help + Say Y here if you have a Cypress PS/2 Trackpad connected to + your system. - If unsure, say Y. + If unsure, say Y. config MOUSE_PS2_LIFEBOOK bool "Fujitsu Lifebook PS/2 mouse protocol extension" if EXPERT
@@ -285,19 +285,19 @@ config MOUSE_ELAN_I2C_I2C depends on MOUSE_ELAN_I2C default y help - Say Y here if Elan Touchpad in your system is connected to - a standard I2C controller. + Say Y here if Elan Touchpad in your system is connected to + a standard I2C controller. - If unsure, say Y. + If unsure, say Y. config MOUSE_ELAN_I2C_SMBUS bool "Enable SMbus support" depends on MOUSE_ELAN_I2C help - Say Y here if Elan Touchpad in your system is connected to - a SMbus adapter. + Say Y here if Elan Touchpad in your system is connected to + a SMbus adapter. - If unsure, say Y. + If unsure, say Y. config MOUSE_INPORT tristate "InPort/MS/ATIXL busmouse"
drivers/input/serio/Kconfig +1 -1
@@ -7,7 +7,7 @@ config SERIO help Say Yes here if you have any input device that uses serial I/O to communicate with the system. This includes the - * standard AT keyboard and PS/2 mouse * + * standard AT keyboard and PS/2 mouse * as well as serial mice, Sun keyboards, some joysticks and 6dof devices and more.
drivers/input/tablet/Kconfig +10 -10
@@ -38,16 +38,16 @@ config TABLET_USB_AIPTEK module will be called aiptek. config TABLET_USB_GTCO - tristate "GTCO CalComp/InterWrite USB Support" - depends on USB && INPUT - help - Say Y here if you want to use the USB version of the GTCO - CalComp/InterWrite Tablet. Make sure to say Y to "Mouse support" - (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" - (CONFIG_INPUT_EVDEV) as well. - - To compile this driver as a module, choose M here: the - module will be called gtco. + tristate "GTCO CalComp/InterWrite USB Support" + depends on USB && INPUT + help + Say Y here if you want to use the USB version of the GTCO + CalComp/InterWrite Tablet. Make sure to say Y to "Mouse support" + (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" + (CONFIG_INPUT_EVDEV) as well. + + To compile this driver as a module, choose M here: the + module will be called gtco. config TABLET_USB_HANWANG tristate "Hanwang Art Master III tablet support (USB)"
drivers/input/touchscreen/Kconfig +1 -1
@@ -632,7 +632,7 @@ config TOUCHSCREEN_HP600 depends on SH_HP6XX && SH_ADC help Say Y here if you have a HP Jornada 620/660/680/690 and want to - support the built-in touchscreen. + support the built-in touchscreen. To compile this driver as a module, choose M here: the module will be called hp680_ts_input.
Signature · 1 line
1.9.1
PATCH 4/114 drivers: watchdog: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/watchdog/Kconfig | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-)
drivers/watchdog/Kconfig +12 -12
@@ -279,10 +279,10 @@ config ARMADA_37XX_WATCHDOG select MFD_SYSCON select WATCHDOG_CORE help - Say Y here to include support for the watchdog timer found on - Marvell Armada 37xx SoCs. - To compile this driver as a module, choose M here: the - module will be called armada_37xx_wdt. + Say Y here to include support for the watchdog timer found on + Marvell Armada 37xx SoCs. + To compile this driver as a module, choose M here: the + module will be called armada_37xx_wdt. config ASM9260_WATCHDOG tristate "Alphascale ASM9260 watchdog"
@@ -606,10 +606,10 @@ config MAX77620_WATCHDOG tristate "Maxim Max77620 Watchdog Timer" depends on MFD_MAX77620 || COMPILE_TEST help - This is the driver for the Max77620 watchdog timer. - Say 'Y' here to enable the watchdog timer support for - MAX77620 chips. To compile this driver as a module, - choose M here: the module will be called max77620_wdt. + This is the driver for the Max77620 watchdog timer. + Say 'Y' here to enable the watchdog timer support for + MAX77620 chips. To compile this driver as a module, + choose M here: the module will be called max77620_wdt. config IMX2_WDT tristate "IMX2+ Watchdog"
@@ -1644,10 +1644,10 @@ config BCM7038_WDT depends on HAS_IOMEM depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST help - Watchdog driver for the built-in hardware in Broadcom 7038 and - later SoCs used in set-top boxes. BCM7038 was made public - during the 2004 CES, and since then, many Broadcom chips use this - watchdog block, including some cable modem chips. + Watchdog driver for the built-in hardware in Broadcom 7038 and + later SoCs used in set-top boxes. BCM7038 was made public + during the 2004 CES, and since then, many Broadcom chips use this + watchdog block, including some cable modem chips. config IMGPDC_WDT tristate "Imagination Technologies PDC Watchdog Timer"
Signature · 1 line
1.9.1
PATCH 5/114 fs: 9p: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- fs/9p/Kconfig | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-)
fs/9p/Kconfig +10 -10
@@ -31,13 +31,13 @@ endif config 9P_FS_SECURITY - bool "9P Security Labels" - depends on 9P_FS - help - Security labels support alternative access control models - implemented by security modules like SELinux. This option - enables an extended attribute handler for file security - labels in the 9P filesystem. - - If you are not using a security module that requires using - extended attributes for file security labels, say N. + bool "9P Security Labels" + depends on 9P_FS + help + Security labels support alternative access control models + implemented by security modules like SELinux. This option + enables an extended attribute handler for file security + labels in the 9P filesystem. + + If you are not using a security module that requires using + extended attributes for file security labels, say N.
Signature · 1 line
1.9.1
PATCH 6/114 drivers: uio: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/uio/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/uio/Kconfig +1 -1
@@ -17,7 +17,7 @@ config UIO_CIF depends on PCI help Driver for Hilscher CIF DeviceNet and Profibus cards. This - driver requires a userspace component called cif that handles + driver requires a userspace component called cif that handles all of the heavy lifting and can be found at: <http://www.osadl.org/projects/downloads/UIO/user/>
Signature · 1 line
1.9.1
PATCH 7/114 drivers: leds: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/leds/Kconfig | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-)
drivers/leds/Kconfig +9 -9
@@ -56,7 +56,7 @@ config LEDS_AAT1290 depends on OF depends on PINCTRL help - This option enables support for the LEDs on the AAT1290. + This option enables support for the LEDs on the AAT1290. config LEDS_AN30259A tristate "LED support for Panasonic AN30259A"
@@ -413,13 +413,13 @@ config LEDS_CLEVO_MAIL This module can drive the mail LED for the following notebooks: - Clevo D400P - Clevo D410J - Clevo D410V - Clevo D400V/D470V (not tested, but might work) - Clevo M540N - Clevo M5x0N (not tested, but might work) - Positivo Mobile (Clevo M5x0V) + Clevo D400P + Clevo D410J + Clevo D410V + Clevo D400V/D470V (not tested, but might work) + Clevo M540N + Clevo M5x0N (not tested, but might work) + Positivo Mobile (Clevo M5x0V) If your model is not listed here you can try the "nodetect" module parameter.
@@ -462,7 +462,7 @@ config LEDS_WM831X_STATUS depends on MFD_WM831X help This option enables support for the status LEDs of the WM831x - series of PMICs. + series of PMICs. config LEDS_WM8350 tristate "LED Support for WM8350 AudioPlus PMIC"
Signature · 1 line
1.9.1
PATCH 8/114 drivers: ata: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/ata/Kconfig | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-)
drivers/ata/Kconfig +9 -9
@@ -32,7 +32,7 @@ menuconfig ATA if ATA config ATA_NONSTANDARD - bool + bool config ATA_VERBOSE_ERROR bool "Verbose ATA error reporting"
@@ -222,7 +222,7 @@ config AHCI_XGENE tristate "APM X-Gene 6.0Gbps AHCI SATA host controller support" depends on PHY_XGENE help - This option enables support for APM X-Gene SoC SATA host controller. + This option enables support for APM X-Gene SoC SATA host controller. config AHCI_QORIQ tristate "Freescale QorIQ AHCI SATA support"
@@ -256,9 +256,9 @@ config SATA_AHCI_SEATTLE tristate "AMD Seattle 6.0Gbps AHCI SATA host controller support" depends on ARCH_SEATTLE help - This option enables support for AMD Seattle SATA host controller. + This option enables support for AMD Seattle SATA host controller. - If unsure, say N + If unsure, say N config SATA_INIC162X tristate "Initio 162x SATA support (Very Experimental)"
@@ -695,7 +695,7 @@ config PATA_IMX depends on ARCH_MXC help This option enables support for the PATA host available on Freescale - iMX SoCs. + iMX SoCs. If unsure, say N.
@@ -704,7 +704,7 @@ config PATA_IT8213 depends on PCI help This option enables support for the ITE 821 PATA - controllers via the new ATA layer. + controllers via the new ATA layer. If unsure, say N.
@@ -732,9 +732,9 @@ config PATA_MACIO depends on PPC_PMAC help Most IDE capable PowerMacs have IDE busses driven by a variant - of this controller which is part of the Apple chipset used on - most PowerMac models. Some models have multiple busses using - different chipsets, though generally, MacIO is one of them. + of this controller which is part of the Apple chipset used on + most PowerMac models. Some models have multiple busses using + different chipsets, though generally, MacIO is one of them. config PATA_MARVELL tristate "Marvell PATA support via legacy mode"
Signature · 1 line
1.9.1
PATCH 9/114 drivers: ide: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/ide/Kconfig | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-)
drivers/ide/Kconfig +13 -13
@@ -320,9 +320,9 @@ config BLK_DEV_OFFBOARD config BLK_DEV_GENERIC tristate "Generic PCI IDE Chipset Support" select BLK_DEV_IDEPCI - help - This option provides generic support for various PCI IDE Chipsets - which otherwise might not be supported. + help + This option provides generic support for various PCI IDE Chipsets + which otherwise might not be supported. config BLK_DEV_OPTI621 tristate "OPTi 82C621 chipset enhanced support"
@@ -516,7 +516,7 @@ config BLK_DEV_IT8213 tristate "IT8213 IDE support" select BLK_DEV_IDEDMA_PCI help - This driver adds support for the ITE 8213 IDE controller. + This driver adds support for the ITE 8213 IDE controller. config BLK_DEV_IT821X tristate "IT821X IDE support"
@@ -671,20 +671,20 @@ config BLK_DEV_IDE_PMAC_ATA100FIRST hard disk and hdc for CD-ROM. config BLK_DEV_IDE_AU1XXX - bool "IDE for AMD Alchemy Au1200" - depends on MIPS_ALCHEMY - select IDE_XFER_MODE + bool "IDE for AMD Alchemy Au1200" + depends on MIPS_ALCHEMY + select IDE_XFER_MODE choice - prompt "IDE Mode for AMD Alchemy Au1200" - default BLK_DEV_IDE_AU1XXX_PIO_DBDMA - depends on BLK_DEV_IDE_AU1XXX + prompt "IDE Mode for AMD Alchemy Au1200" + default BLK_DEV_IDE_AU1XXX_PIO_DBDMA + depends on BLK_DEV_IDE_AU1XXX config BLK_DEV_IDE_AU1XXX_PIO_DBDMA - bool "PIO+DbDMA IDE for AMD Alchemy Au1200" + bool "PIO+DbDMA IDE for AMD Alchemy Au1200" config BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA - bool "MDMA2+DbDMA IDE for AMD Alchemy Au1200" - depends on BLK_DEV_IDE_AU1XXX + bool "MDMA2+DbDMA IDE for AMD Alchemy Au1200" + depends on BLK_DEV_IDE_AU1XXX endchoice config BLK_DEV_IDE_TX4938
Signature · 1 line
1.9.1
PATCH 10/114 sound: soc: qcom: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- sound/soc/qcom/Kconfig | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-)
sound/soc/qcom/Kconfig +14 -14
@@ -2,8 +2,8 @@ config SND_SOC_QCOM tristate "ASoC support for QCOM platforms" depends on ARCH_QCOM || COMPILE_TEST help - Say Y or M if you want to add support to use audio devices - in Qualcomm Technologies SOC-based platforms. + Say Y or M if you want to add support to use audio devices + in Qualcomm Technologies SOC-based platforms. config SND_SOC_LPASS_CPU tristate
@@ -29,17 +29,17 @@ config SND_SOC_STORM select SND_SOC_LPASS_IPQ806X select SND_SOC_MAX98357A help - Say Y or M if you want add support for SoC audio on the - Qualcomm Technologies IPQ806X-based Storm board. + Say Y or M if you want add support for SoC audio on the + Qualcomm Technologies IPQ806X-based Storm board. config SND_SOC_APQ8016_SBC tristate "SoC Audio support for APQ8016 SBC platforms" depends on SND_SOC_QCOM select SND_SOC_LPASS_APQ8016 help - Support for Qualcomm Technologies LPASS audio block in - APQ8016 SOC-based systems. - Say Y if you want to use audio devices on MI2S. + Support for Qualcomm Technologies LPASS audio block in + APQ8016 SOC-based systems. + Say Y if you want to use audio devices on MI2S. config SND_SOC_QCOM_COMMON tristate
@@ -81,10 +81,10 @@ config SND_SOC_QDSP6 select SND_SOC_QDSP6_ASM select SND_SOC_QDSP6_ASM_DAI help - To add support for MSM QDSP6 Soc Audio. - This will enable sound soc platform specific - audio drivers. This includes q6asm, q6adm, - q6afe interfaces to DSP using apr. + To add support for MSM QDSP6 Soc Audio. + This will enable sound soc platform specific + audio drivers. This includes q6asm, q6adm, + q6afe interfaces to DSP using apr. config SND_SOC_MSM8996 tristate "SoC Machine driver for MSM8996 and APQ8096 boards"
@@ -92,9 +92,9 @@ config SND_SOC_MSM8996 select SND_SOC_QDSP6 select SND_SOC_QCOM_COMMON help - Support for Qualcomm Technologies LPASS audio block in - APQ8096 SoC-based systems. - Say Y if you want to use audio device on this SoCs + Support for Qualcomm Technologies LPASS audio block in + APQ8096 SoC-based systems. + Say Y if you want to use audio device on this SoCs config SND_SOC_SDM845 tristate "SoC Machine driver for SDM845 boards"
Signature · 1 line
1.9.1
PATCH 11/114 drivers: mmc: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/mmc/host/Kconfig | 43 ++++++++++++++++++++++--------------------- 1 file changed, 22 insertions(+), 21 deletions(-)
drivers/mmc/host/Kconfig +22 -21
@@ -437,7 +437,7 @@ config MMC_WBSD depends on ISA_DMA_API help This selects the Winbond(R) W83L51xD Secure digital and - Multimedia card Interface. + Multimedia card Interface. If you have a machine with a integrated W83L518D or W83L519D SD/MMC card reader, say Y or M here.
@@ -515,7 +515,7 @@ config MMC_TIFM_SD 'Misc devices: TI Flash Media PCI74xx/PCI76xx host adapter support (TIFM_7XX1)'. - To compile this driver as a module, choose M here: the + To compile this driver as a module, choose M here: the module will be called tifm_sd. config MMC_MVSDIO
@@ -531,12 +531,12 @@ config MMC_MVSDIO module will be called mvsdio. config MMC_DAVINCI - tristate "TI DAVINCI Multimedia Card Interface support" - depends on ARCH_DAVINCI - help - This selects the TI DAVINCI Multimedia card Interface. - If you have an DAVINCI board with a Multimedia Card slot, - say Y or M here. If unsure, say N. + tristate "TI DAVINCI Multimedia Card Interface support" + depends on ARCH_DAVINCI + help + This selects the TI DAVINCI Multimedia card Interface. + If you have an DAVINCI board with a Multimedia Card slot, + say Y or M here. If unsure, say N. config MMC_GOLDFISH tristate "goldfish qemu Multimedia Card Interface support"
@@ -565,18 +565,18 @@ config MMC_S3C depends on S3C24XX_DMAC help This selects a driver for the MCI interface found in - Samsung's S3C2410, S3C2412, S3C2440, S3C2442 CPUs. + Samsung's S3C2410, S3C2412, S3C2440, S3C2442 CPUs. If you have a board based on one of those and a MMC/SD slot, say Y or M here. If unsure, say N. config MMC_S3C_HW_SDIO_IRQ - bool "Hardware support for SDIO IRQ" - depends on MMC_S3C - help - Enable the hardware support for SDIO interrupts instead of using - the generic polling code. + bool "Hardware support for SDIO IRQ" + depends on MMC_S3C + help + Enable the hardware support for SDIO interrupts instead of using + the generic polling code. choice prompt "Samsung S3C SD/MMC transfer code"
@@ -948,15 +948,16 @@ config MMC_MTK If unsure, say N. config MMC_SDHCI_MICROCHIP_PIC32 - tristate "Microchip PIC32MZDA SDHCI support" - depends on MMC_SDHCI && PIC32MZDA && MMC_SDHCI_PLTFM - help - This selects the Secure Digital Host Controller Interface (SDHCI) - for PIC32MZDA platform. + tristate "Microchip PIC32MZDA SDHCI support" + depends on MMC_SDHCI && PIC32MZDA && MMC_SDHCI_PLTFM + help + This selects the Secure Digital Host Controller Interface (SDHCI) + for PIC32MZDA platform. + + If you have a controller with this interface, say Y or M here. - If you have a controller with this interface, say Y or M here. + If unsure, say N. - If unsure, say N. config MMC_SDHCI_BRCMSTB tristate "Broadcom SDIO/SD/MMC support" depends on ARCH_BRCMSTB || BMIPS_GENERIC
Signature · 1 line
1.9.1
PATCH 12/114 arch: um: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/um/Kconfig | 52 ++++++++++++++++++++++++++-------------------------- 1 file changed, 26 insertions(+), 26 deletions(-)
arch/um/Kconfig +26 -26
@@ -80,46 +80,46 @@ config LD_SCRIPT_DYN bool default y depends on !LD_SCRIPT_STATIC - select MODULE_REL_CRCS if MODVERSIONS + select MODULE_REL_CRCS if MODVERSIONS config HOSTFS tristate "Host filesystem" help - While the User-Mode Linux port uses its own root file system for - booting and normal file access, this module lets the UML user - access files stored on the host. It does not require any - network connection between the Host and UML. An example use of - this might be: + While the User-Mode Linux port uses its own root file system for + booting and normal file access, this module lets the UML user + access files stored on the host. It does not require any + network connection between the Host and UML. An example use of + this might be: - mount none /tmp/fromhost -t hostfs -o /tmp/umlshare + mount none /tmp/fromhost -t hostfs -o /tmp/umlshare - where /tmp/fromhost is an empty directory inside UML and - /tmp/umlshare is a directory on the host with files the UML user - wishes to access. + where /tmp/fromhost is an empty directory inside UML and + /tmp/umlshare is a directory on the host with files the UML user + wishes to access. - For more information, see - <http://user-mode-linux.sourceforge.net/hostfs.html>. + For more information, see + <http://user-mode-linux.sourceforge.net/hostfs.html>. - If you'd like to be able to work with files stored on the host, - say Y or M here; otherwise say N. + If you'd like to be able to work with files stored on the host, + say Y or M here; otherwise say N. config MCONSOLE bool "Management console" depends on PROC_FS default y help - The user mode linux management console is a low-level interface to - the kernel, somewhat like the i386 SysRq interface. Since there is - a full-blown operating system running under every user mode linux - instance, there is much greater flexibility possible than with the - SysRq mechanism. - - If you answer 'Y' to this option, to use this feature, you need the - mconsole client (called uml_mconsole) which is present in CVS in - 2.4.5-9um and later (path /tools/mconsole), and is also in the - distribution RPM package in 2.4.6 and later. - - It is safe to say 'Y' here. + The user mode linux management console is a low-level interface to + the kernel, somewhat like the i386 SysRq interface. Since there is + a full-blown operating system running under every user mode linux + instance, there is much greater flexibility possible than with the + SysRq mechanism. + + If you answer 'Y' to this option, to use this feature, you need the + mconsole client (called uml_mconsole) which is present in CVS in + 2.4.5-9um and later (path /tools/mconsole), and is also in the + distribution RPM package in 2.4.6 and later. + + It is safe to say 'Y' here. config MAGIC_SYSRQ bool "Magic SysRq key"
Signature · 1 line
1.9.1
PATCH 13/114 arch: um: drivers: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/um/drivers/Kconfig | 352 ++++++++++++++++++++++++------------------------ 1 file changed, 176 insertions(+), 176 deletions(-)
arch/um/drivers/Kconfig +176 -176
@@ -11,58 +11,58 @@ config STDERR_CONSOLE config SSL bool "Virtual serial line" help - The User-Mode Linux environment allows you to create virtual serial - lines on the UML that are usually made to show up on the host as - ttys or ptys. + The User-Mode Linux environment allows you to create virtual serial + lines on the UML that are usually made to show up on the host as + ttys or ptys. - See <http://user-mode-linux.sourceforge.net/old/input.html> for more - information and command line examples of how to use this facility. + See <http://user-mode-linux.sourceforge.net/old/input.html> for more + information and command line examples of how to use this facility. - Unless you have a specific reason for disabling this, say Y. + Unless you have a specific reason for disabling this, say Y. config NULL_CHAN bool "null channel support" help - This option enables support for attaching UML consoles and serial - lines to a device similar to /dev/null. Data written to it disappears - and there is never any data to be read. + This option enables support for attaching UML consoles and serial + lines to a device similar to /dev/null. Data written to it disappears + and there is never any data to be read. config PORT_CHAN bool "port channel support" help - This option enables support for attaching UML consoles and serial - lines to host portals. They may be accessed with 'telnet <host> - <port number>'. Any number of consoles and serial lines may be - attached to a single portal, although what UML device you get when - you telnet to that portal will be unpredictable. - It is safe to say 'Y' here. + This option enables support for attaching UML consoles and serial + lines to host portals. They may be accessed with 'telnet <host> + <port number>'. Any number of consoles and serial lines may be + attached to a single portal, although what UML device you get when + you telnet to that portal will be unpredictable. + It is safe to say 'Y' here. config PTY_CHAN bool "pty channel support" help - This option enables support for attaching UML consoles and serial - lines to host pseudo-terminals. Access to both traditional - pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled - with this option. The assignment of UML devices to host devices - will be announced in the kernel message log. - It is safe to say 'Y' here. + This option enables support for attaching UML consoles and serial + lines to host pseudo-terminals. Access to both traditional + pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled + with this option. The assignment of UML devices to host devices + will be announced in the kernel message log. + It is safe to say 'Y' here. config TTY_CHAN bool "tty channel support" help - This option enables support for attaching UML consoles and serial - lines to host terminals. Access to both virtual consoles - (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and - /dev/pts/*) are controlled by this option. - It is safe to say 'Y' here. + This option enables support for attaching UML consoles and serial + lines to host terminals. Access to both virtual consoles + (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and + /dev/pts/*) are controlled by this option. + It is safe to say 'Y' here. config XTERM_CHAN bool "xterm channel support" help - This option enables support for attaching UML consoles and serial - lines to xterms. Each UML device so assigned will be brought up in - its own xterm. - It is safe to say 'Y' here. + This option enables support for attaching UML consoles and serial + lines to xterms. Each UML device so assigned will be brought up in + its own xterm. + It is safe to say 'Y' here. config NOCONFIG_CHAN bool
@@ -72,43 +72,43 @@ config CON_ZERO_CHAN string "Default main console channel initialization" default "fd:0,fd:1" help - This is the string describing the channel to which the main console - will be attached by default. This value can be overridden from the - command line. The default value is "fd:0,fd:1", which attaches the - main console to stdin and stdout. - It is safe to leave this unchanged. + This is the string describing the channel to which the main console + will be attached by default. This value can be overridden from the + command line. The default value is "fd:0,fd:1", which attaches the + main console to stdin and stdout. + It is safe to leave this unchanged. config CON_CHAN string "Default console channel initialization" default "xterm" help - This is the string describing the channel to which all consoles - except the main console will be attached by default. This value can - be overridden from the command line. The default value is "xterm", - which brings them up in xterms. - It is safe to leave this unchanged, although you may wish to change - this if you expect the UML that you build to be run in environments - which don't have X or xterm available. + This is the string describing the channel to which all consoles + except the main console will be attached by default. This value can + be overridden from the command line. The default value is "xterm", + which brings them up in xterms. + It is safe to leave this unchanged, although you may wish to change + this if you expect the UML that you build to be run in environments + which don't have X or xterm available. config SSL_CHAN string "Default serial line channel initialization" default "pty" help - This is the string describing the channel to which the serial lines - will be attached by default. This value can be overridden from the - command line. The default value is "pty", which attaches them to - traditional pseudo-terminals. - It is safe to leave this unchanged, although you may wish to change - this if you expect the UML that you build to be run in environments - which don't have a set of /dev/pty* devices. + This is the string describing the channel to which the serial lines + will be attached by default. This value can be overridden from the + command line. The default value is "pty", which attaches them to + traditional pseudo-terminals. + It is safe to leave this unchanged, although you may wish to change + this if you expect the UML that you build to be run in environments + which don't have a set of /dev/pty* devices. config UML_SOUND tristate "Sound support" help - This option enables UML sound support. If enabled, it will pull in - soundcore and the UML hostaudio relay, which acts as a intermediary - between the host's dsp and mixer devices and the UML sound system. - It is safe to say 'Y' here. + This option enables UML sound support. If enabled, it will pull in + soundcore and the UML hostaudio relay, which acts as a intermediary + between the host's dsp and mixer devices and the UML sound system. + It is safe to say 'Y' here. config SOUND tristate
@@ -131,107 +131,107 @@ menu "UML Network Devices" config UML_NET bool "Virtual network device" help - While the User-Mode port cannot directly talk to any physical - hardware devices, this choice and the following transport options - provide one or more virtual network devices through which the UML - kernels can talk to each other, the host, and with the host's help, - machines on the outside world. + While the User-Mode port cannot directly talk to any physical + hardware devices, this choice and the following transport options + provide one or more virtual network devices through which the UML + kernels can talk to each other, the host, and with the host's help, + machines on the outside world. - For more information, including explanations of the networking and - sample configurations, see - <http://user-mode-linux.sourceforge.net/old/networking.html>. + For more information, including explanations of the networking and + sample configurations, see + <http://user-mode-linux.sourceforge.net/old/networking.html>. - If you'd like to be able to enable networking in the User-Mode - linux environment, say Y; otherwise say N. Note that you must - enable at least one of the following transport options to actually - make use of UML networking. + If you'd like to be able to enable networking in the User-Mode + linux environment, say Y; otherwise say N. Note that you must + enable at least one of the following transport options to actually + make use of UML networking. config UML_NET_ETHERTAP bool "Ethertap transport" depends on UML_NET help - The Ethertap User-Mode Linux network transport allows a single - running UML to exchange packets with its host over one of the - host's Ethertap devices, such as /dev/tap0. Additional running - UMLs can use additional Ethertap devices, one per running UML. - While the UML believes it's on a (multi-device, broadcast) virtual - Ethernet network, it's in fact communicating over a point-to-point - link with the host. - - To use this, your host kernel must have support for Ethertap - devices. Also, if your host kernel is 2.4.x, it must have - CONFIG_NETLINK_DEV configured as Y or M. - - For more information, see - <http://user-mode-linux.sourceforge.net/old/networking.html> That site - has examples of the UML command line to use to enable Ethertap - networking. - - If you'd like to set up an IP network with the host and/or the - outside world, say Y to this, the Daemon Transport and/or the - Slip Transport. You'll need at least one of them, but may choose - more than one without conflict. If you don't need UML networking, - say N. + The Ethertap User-Mode Linux network transport allows a single + running UML to exchange packets with its host over one of the + host's Ethertap devices, such as /dev/tap0. Additional running + UMLs can use additional Ethertap devices, one per running UML. + While the UML believes it's on a (multi-device, broadcast) virtual + Ethernet network, it's in fact communicating over a point-to-point + link with the host. + + To use this, your host kernel must have support for Ethertap + devices. Also, if your host kernel is 2.4.x, it must have + CONFIG_NETLINK_DEV configured as Y or M. + + For more information, see + <http://user-mode-linux.sourceforge.net/old/networking.html> That site + has examples of the UML command line to use to enable Ethertap + networking. + + If you'd like to set up an IP network with the host and/or the + outside world, say Y to this, the Daemon Transport and/or the + Slip Transport. You'll need at least one of them, but may choose + more than one without conflict. If you don't need UML networking, + say N. config UML_NET_TUNTAP bool "TUN/TAP transport" depends on UML_NET help - The UML TUN/TAP network transport allows a UML instance to exchange - packets with the host over a TUN/TAP device. This option will only - work with a 2.4 host, unless you've applied the TUN/TAP patch to - your 2.2 host kernel. + The UML TUN/TAP network transport allows a UML instance to exchange + packets with the host over a TUN/TAP device. This option will only + work with a 2.4 host, unless you've applied the TUN/TAP patch to + your 2.2 host kernel. - To use this transport, your host kernel must have support for TUN/TAP - devices, either built-in or as a module. + To use this transport, your host kernel must have support for TUN/TAP + devices, either built-in or as a module. config UML_NET_SLIP bool "SLIP transport" depends on UML_NET help - The slip User-Mode Linux network transport allows a running UML to - network with its host over a point-to-point link. Unlike Ethertap, - which can carry any Ethernet frame (and hence even non-IP packets), - the slip transport can only carry IP packets. - - To use this, your host must support slip devices. - - For more information, see - <http://user-mode-linux.sourceforge.net/old/networking.html>. - has examples of the UML command line to use to enable slip - networking, and details of a few quirks with it. - - The Ethertap Transport is preferred over slip because of its - limitations. If you prefer slip, however, say Y here. Otherwise - choose the Multicast transport (to network multiple UMLs on - multiple hosts), Ethertap (to network with the host and the - outside world), and/or the Daemon transport (to network multiple - UMLs on a single host). You may choose more than one without - conflict. If you don't need UML networking, say N. + The slip User-Mode Linux network transport allows a running UML to + network with its host over a point-to-point link. Unlike Ethertap, + which can carry any Ethernet frame (and hence even non-IP packets), + the slip transport can only carry IP packets. + + To use this, your host must support slip devices. + + For more information, see + <http://user-mode-linux.sourceforge.net/old/networking.html>. + has examples of the UML command line to use to enable slip + networking, and details of a few quirks with it. + + The Ethertap Transport is preferred over slip because of its + limitations. If you prefer slip, however, say Y here. Otherwise + choose the Multicast transport (to network multiple UMLs on + multiple hosts), Ethertap (to network with the host and the + outside world), and/or the Daemon transport (to network multiple + UMLs on a single host). You may choose more than one without + conflict. If you don't need UML networking, say N. config UML_NET_DAEMON bool "Daemon transport" depends on UML_NET help - This User-Mode Linux network transport allows one or more running - UMLs on a single host to communicate with each other, but not to - the host. - - To use this form of networking, you'll need to run the UML - networking daemon on the host. - - For more information, see - <http://user-mode-linux.sourceforge.net/old/networking.html> That site - has examples of the UML command line to use to enable Daemon - networking. - - If you'd like to set up a network with other UMLs on a single host, - say Y. If you need a network between UMLs on multiple physical - hosts, choose the Multicast Transport. To set up a network with - the host and/or other IP machines, say Y to the Ethertap or Slip - transports. You'll need at least one of them, but may choose - more than one without conflict. If you don't need UML networking, - say N. + This User-Mode Linux network transport allows one or more running + UMLs on a single host to communicate with each other, but not to + the host. + + To use this form of networking, you'll need to run the UML + networking daemon on the host. + + For more information, see + <http://user-mode-linux.sourceforge.net/old/networking.html> That site + has examples of the UML command line to use to enable Daemon + networking. + + If you'd like to set up a network with other UMLs on a single host, + say Y. If you need a network between UMLs on multiple physical + hosts, choose the Multicast Transport. To set up a network with + the host and/or other IP machines, say Y to the Ethertap or Slip + transports. You'll need at least one of them, but may choose + more than one without conflict. If you don't need UML networking, + say N. config UML_NET_VECTOR bool "Vector I/O high performance network devices"
@@ -270,26 +270,26 @@ config UML_NET_MCAST bool "Multicast transport" depends on UML_NET help - This Multicast User-Mode Linux network transport allows multiple - UMLs (even ones running on different host machines!) to talk to - each other over a virtual ethernet network. However, it requires - at least one UML with one of the other transports to act as a - bridge if any of them need to be able to talk to their hosts or any - other IP machines. - - To use this, your host kernel(s) must support IP Multicasting. - - For more information, see - <http://user-mode-linux.sourceforge.net/old/networking.html> That site - has examples of the UML command line to use to enable Multicast - networking, and notes about the security of this approach. - - If you need UMLs on multiple physical hosts to communicate as if - they shared an Ethernet network, say Y. If you need to communicate - with other IP machines, make sure you select one of the other - transports (possibly in addition to Multicast; they're not - exclusive). If you don't need to network UMLs say N to each of - the transports. + This Multicast User-Mode Linux network transport allows multiple + UMLs (even ones running on different host machines!) to talk to + each other over a virtual ethernet network. However, it requires + at least one UML with one of the other transports to act as a + bridge if any of them need to be able to talk to their hosts or any + other IP machines. + + To use this, your host kernel(s) must support IP Multicasting. + + For more information, see + <http://user-mode-linux.sourceforge.net/old/networking.html> That site + has examples of the UML command line to use to enable Multicast + networking, and notes about the security of this approach. + + If you need UMLs on multiple physical hosts to communicate as if + they shared an Ethernet network, say Y. If you need to communicate + with other IP machines, make sure you select one of the other + transports (possibly in addition to Multicast; they're not + exclusive). If you don't need to network UMLs say N to each of + the transports. config UML_NET_PCAP bool "pcap transport"
@@ -300,9 +300,9 @@ config UML_NET_PCAP UML act as a network monitor for the host. You must have libcap installed in order to build the pcap transport into UML. - For more information, see - <http://user-mode-linux.sourceforge.net/old/networking.html> That site - has examples of the UML command line to use to enable this option. + For more information, see + <http://user-mode-linux.sourceforge.net/old/networking.html> That site + has examples of the UML command line to use to enable this option. If you intend to use UML as a network monitor for the host, say Y here. Otherwise, say N.
@@ -311,27 +311,27 @@ config UML_NET_SLIRP bool "SLiRP transport" depends on UML_NET help - The SLiRP User-Mode Linux network transport allows a running UML - to network by invoking a program that can handle SLIP encapsulated - packets. This is commonly (but not limited to) the application - known as SLiRP, a program that can re-socket IP packets back onto - the host on which it is run. Only IP packets are supported, - unlike other network transports that can handle all Ethernet - frames. In general, slirp allows the UML the same IP connectivity - to the outside world that the host user is permitted, and unlike - other transports, SLiRP works without the need of root level - privleges, setuid binaries, or SLIP devices on the host. This - also means not every type of connection is possible, but most - situations can be accommodated with carefully crafted slirp - commands that can be passed along as part of the network device's - setup string. The effect of this transport on the UML is similar - that of a host behind a firewall that masquerades all network - connections passing through it (but is less secure). - - To use this you should first have slirp compiled somewhere - accessible on the host, and have read its documentation. If you - don't need UML networking, say N. - - Startup example: "eth0=slirp,FE:FD:01:02:03:04,/usr/local/bin/slirp" + The SLiRP User-Mode Linux network transport allows a running UML + to network by invoking a program that can handle SLIP encapsulated + packets. This is commonly (but not limited to) the application + known as SLiRP, a program that can re-socket IP packets back onto + he host on which it is run. Only IP packets are supported, + unlike other network transports that can handle all Ethernet + frames. In general, slirp allows the UML the same IP connectivity + to the outside world that the host user is permitted, and unlike + other transports, SLiRP works without the need of root level + privleges, setuid binaries, or SLIP devices on the host. This + also means not every type of connection is possible, but most + situations can be accommodated with carefully crafted slirp + commands that can be passed along as part of the network device's + setup string. The effect of this transport on the UML is similar + that of a host behind a firewall that masquerades all network + connections passing through it (but is less secure). + + To use this you should first have slirp compiled somewhere + accessible on the host, and have read its documentation. If you + don't need UML networking, say N. + + Startup example: "eth0=slirp,FE:FD:01:02:03:04,/usr/local/bin/slirp" endmenu
Signature · 1 line
1.9.1
PATCH 14/114 drivers: fpga: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/fpga/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/fpga/Kconfig +3 -3
@@ -25,9 +25,9 @@ config FPGA_MGR_SOCFPGA_A10 FPGA manager driver support for Altera Arria10 SoCFPGA. config ALTERA_PR_IP_CORE - tristate "Altera Partial Reconfiguration IP Core" - help - Core driver support for Altera Partial Reconfiguration IP component + tristate "Altera Partial Reconfiguration IP Core" + help + Core driver support for Altera Partial Reconfiguration IP component config ALTERA_PR_IP_CORE_PLAT tristate "Platform support of Altera Partial Reconfiguration IP Core"
Signature · 1 line
1.9.1
PATCH 15/114 drivers: nvme: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/nvme/host/Kconfig | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/nvme/host/Kconfig +4 -4
@@ -17,10 +17,10 @@ config NVME_MULTIPATH bool "NVMe multipath support" depends on NVME_CORE ---help--- - This option enables support for multipath access to NVMe - subsystems. If this option is enabled only a single - /dev/nvmeXnY device will show up for each NVMe namespaces, - even if it is accessible through multiple controllers. + This option enables support for multipath access to NVMe + subsystems. If this option is enabled only a single + /dev/nvmeXnY device will show up for each NVMe namespaces, + even if it is accessible through multiple controllers. config NVME_FABRICS tristate
Signature · 1 line
1.9.1
PATCH 16/114 drivers: pcmcia: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/pcmcia/Kconfig | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-)
drivers/pcmcia/Kconfig +10 -10
@@ -22,18 +22,18 @@ config PCMCIA select CRC32 default y ---help--- - This option enables support for 16-bit PCMCIA cards. Most older - PC-cards are such 16-bit PCMCIA cards, so unless you know you're - only using 32-bit CardBus cards, say Y or M here. + This option enables support for 16-bit PCMCIA cards. Most older + PC-cards are such 16-bit PCMCIA cards, so unless you know you're + only using 32-bit CardBus cards, say Y or M here. - To use 16-bit PCMCIA cards, you will need supporting software in - most cases. (see the file <file:Documentation/Changes> for - location and details). + To use 16-bit PCMCIA cards, you will need supporting software in + most cases. (see the file <file:Documentation/Changes> for + location and details). - To compile this driver as modules, choose M here: the - module will be called pcmcia. + To compile this driver as modules, choose M here: the + module will be called pcmcia. - If unsure, say Y. + If unsure, say Y. config PCMCIA_LOAD_CIS bool "Load CIS updates from userspace"
@@ -275,4 +275,4 @@ config PCCARD_NONSTATIC config PCCARD_IODYN bool -endif # PCCARD +endif # PCCARD
Signature · 1 line
1.9.1
PATCH 17/114 drivers: infiniband: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/infiniband/hw/bnxt_re/Kconfig | 12 ++++++------ drivers/infiniband/ulp/iser/Kconfig | 4 ++-- 2 files changed, 8 insertions(+), 8 deletions(-)
drivers/infiniband/hw/bnxt_re/Kconfig +6 -6
@@ -1,10 +1,10 @@ config INFINIBAND_BNXT_RE - tristate "Broadcom Netxtreme HCA support" - depends on 64BIT - depends on ETHERNET && NETDEVICES && PCI && INET && DCB - select NET_VENDOR_BROADCOM - select BNXT - ---help--- + tristate "Broadcom Netxtreme HCA support" + depends on 64BIT + depends on ETHERNET && NETDEVICES && PCI && INET && DCB + select NET_VENDOR_BROADCOM + select BNXT + ---help--- This driver supports Broadcom NetXtreme-E 10/25/40/50 gigabit RoCE HCAs. To compile this driver as a module, choose M here: the module will be called bnxt_re.
drivers/infiniband/ulp/iser/Kconfig +2 -2
@@ -4,8 +4,8 @@ config INFINIBAND_ISER select SCSI_ISCSI_ATTRS ---help--- Support for the iSCSI Extensions for RDMA (iSER) Protocol - over InfiniBand. This allows you to access storage devices - that speak iSCSI over iSER over InfiniBand. + over InfiniBand. This allows you to access storage devices + that speak iSCSI over iSER over InfiniBand. The iSER protocol is defined by IETF. See <http://www.ietf.org/rfc/rfc5046.txt>
Signature · 1 line
1.9.1
PATCH 18/114 drivers: ntb: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/ntb/Kconfig | 20 ++++++++++---------- drivers/ntb/hw/amd/Kconfig | 4 ++-- drivers/ntb/hw/idt/Kconfig | 41 ++++++++++++++++++++--------------------- drivers/ntb/hw/intel/Kconfig | 4 ++-- drivers/ntb/hw/mscc/Kconfig | 8 ++++---- drivers/ntb/test/Kconfig | 26 +++++++++++++------------- 6 files changed, 51 insertions(+), 52 deletions(-)
drivers/ntb/Kconfig +10 -10
@@ -2,13 +2,13 @@ menuconfig NTB tristate "Non-Transparent Bridge support" depends on PCI help - The PCI-E Non-transparent bridge hardware is a point-to-point PCI-E bus - connecting 2 systems. When configured, writes to the device's PCI - mapped memory will be mirrored to a buffer on the remote system. The - ntb Linux driver uses this point-to-point communication as a method to - transfer data from one system to the other. + The PCI-E Non-transparent bridge hardware is a point-to-point PCI-E bus + connecting 2 systems. When configured, writes to the device's PCI + mapped memory will be mirrored to a buffer on the remote system. The + ntb Linux driver uses this point-to-point communication as a method to + transfer data from one system to the other. - If unsure, say N. + If unsure, say N. if NTB
@@ -19,10 +19,10 @@ source "drivers/ntb/test/Kconfig" config NTB_TRANSPORT tristate "NTB Transport Client" help - This is a transport driver that enables connected systems to exchange - messages over the ntb hardware. The transport exposes a queue pair api - to client drivers. + This is a transport driver that enables connected systems to exchange + messages over the ntb hardware. The transport exposes a queue pair api + to client drivers. - If unsure, say N. + If unsure, say N. endif # NTB
drivers/ntb/hw/amd/Kconfig +2 -2
@@ -2,6 +2,6 @@ config NTB_AMD tristate "AMD Non-Transparent Bridge support" depends on X86_64 help - This driver supports AMD NTB on capable Zeppelin hardware. + This driver supports AMD NTB on capable Zeppelin hardware. - If unsure, say N. + If unsure, say N.
drivers/ntb/hw/idt/Kconfig +20 -21
48 lines not on this page · raw message
drivers/ntb/hw/intel/Kconfig +2 -2
@@ -2,6 +2,6 @@ config NTB_INTEL tristate "Intel Non-Transparent Bridge support" depends on X86_64 help - This driver supports Intel NTB on capable Xeon and Atom hardware. + This driver supports Intel NTB on capable Xeon and Atom hardware. - If unsure, say N. + If unsure, say N.
drivers/ntb/hw/mscc/Kconfig +4 -4
@@ -2,8 +2,8 @@ config NTB_SWITCHTEC tristate "MicroSemi Switchtec Non-Transparent Bridge Support" select PCI_SW_SWITCHTEC help - Enables NTB support for Switchtec PCI switches. This also - selects the Switchtec management driver as they share the same - hardware interface. + Enables NTB support for Switchtec PCI switches. This also + selects the Switchtec management driver as they share the same + hardware interface. - If unsure, say N. + If unsure, say N.
drivers/ntb/test/Kconfig +13 -13
@@ -1,27 +1,27 @@ config NTB_PINGPONG tristate "NTB Ping Pong Test Client" help - This is a simple ping pong driver that exercises the scratchpads and - doorbells of the ntb hardware. This driver may be used to test that - your ntb hardware and drivers are functioning at a basic level. + This is a simple ping pong driver that exercises the scratchpads and + doorbells of the ntb hardware. This driver may be used to test that + your ntb hardware and drivers are functioning at a basic level. - If unsure, say N. + If unsure, say N. config NTB_TOOL tristate "NTB Debugging Tool Test Client" help - This is a simple debugging driver that enables the doorbell and - scratchpad registers to be read and written from the debugfs. This - enables more complicated debugging to be scripted from user space. - This driver may be used to test that your ntb hardware and drivers are - functioning at a basic level. + This is a simple debugging driver that enables the doorbell and + scratchpad registers to be read and written from the debugfs. This + enables more complicated debugging to be scripted from user space. + This driver may be used to test that your ntb hardware and drivers are + functioning at a basic level. - If unsure, say N. + If unsure, say N. config NTB_PERF tristate "NTB RAW Perf Measuring Tool" help - This is a tool to measure raw NTB performance by transferring data - to and from the window without additional software interaction. + This is a tool to measure raw NTB performance by transferring data + to and from the window without additional software interaction. - If unsure, say N. + If unsure, say N.
Signature · 1 line
1.9.1
PATCH 19/114 drivers: uwb: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/uwb/Kconfig | 42 +++++++++++++++++++++--------------------- 1 file changed, 21 insertions(+), 21 deletions(-)
drivers/uwb/Kconfig +21 -21
@@ -41,31 +41,31 @@ config UWB_HWA is safe to select any even if you do not have the hardware. config UWB_WHCI - tristate "UWB Radio Control driver for WHCI-compliant cards" - depends on PCI - help - This driver enables the radio controller for WHCI cards. + tristate "UWB Radio Control driver for WHCI-compliant cards" + depends on PCI + help + This driver enables the radio controller for WHCI cards. - WHCI is a specification developed by Intel - (http://www.intel.com/technology/comms/wusb/whci.htm) much - in the spirit of USB's EHCI, but for UWB and Wireless USB - radio/host controllers connected via memory mapping (eg: - PCI). Most of these cards come also with a Wireless USB host - controller. + WHCI is a specification developed by Intel + (http://www.intel.com/technology/comms/wusb/whci.htm) much + in the spirit of USB's EHCI, but for UWB and Wireless USB + radio/host controllers connected via memory mapping (eg: + PCI). Most of these cards come also with a Wireless USB host + controller. - To compile this driver select Y (built in) or M (module). It - is safe to select any even if you do not have the hardware. + To compile this driver select Y (built in) or M (module). It + is safe to select any even if you do not have the hardware. config UWB_I1480U - tristate "Support for Intel Wireless UWB Link 1480 HWA" - depends on UWB_HWA - select FW_LOADER - help - This driver enables support for the i1480 when connected via - USB. It consists of a firmware uploader that will enable it - to behave as an HWA device. + tristate "Support for Intel Wireless UWB Link 1480 HWA" + depends on UWB_HWA + select FW_LOADER + help + This driver enables support for the i1480 when connected via + USB. It consists of a firmware uploader that will enable it + to behave as an HWA device. - To compile this driver select Y (built in) or M (module). It - is safe to select any even if you do not have the hardware. + To compile this driver select Y (built in) or M (module). It + is safe to select any even if you do not have the hardware. endif # UWB
Signature · 1 line
1.9.1
PATCH 20/114 drivers: thermal: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/thermal/st/Kconfig | 22 +++++++++++----------- drivers/thermal/tegra/Kconfig | 4 ++-- 2 files changed, 13 insertions(+), 13 deletions(-)
drivers/thermal/st/Kconfig +11 -11
@@ -3,9 +3,9 @@ # config ST_THERMAL - tristate "Thermal sensors on STMicroelectronics STi series of SoCs" - help - Support for thermal sensors on STMicroelectronics STi series of SoCs. + tristate "Thermal sensors on STMicroelectronics STi series of SoCs" + help + Support for thermal sensors on STMicroelectronics STi series of SoCs. config ST_THERMAL_SYSCFG select ST_THERMAL
@@ -16,11 +16,11 @@ config ST_THERMAL_MEMMAP tristate "STi series memory mapped access based thermal sensors" config STM32_THERMAL - tristate "Thermal framework support on STMicroelectronics STM32 series of SoCs" - depends on MACH_STM32MP157 - default y - help - Support for thermal framework on STMicroelectronics STM32 series of - SoCs. This thermal driver allows to access to general thermal framework - functionalities and to acces to SoC sensor functionalities. This - configuration is fully dependent of MACH_STM32MP157. + tristate "Thermal framework support on STMicroelectronics STM32 series of SoCs" + depends on MACH_STM32MP157 + default y + help + Support for thermal framework on STMicroelectronics STM32 series of + SoCs. This thermal driver allows to access to general thermal framework + functionalities and to acces to SoC sensor functionalities. This + configuration is fully dependent of MACH_STM32MP157.
drivers/thermal/tegra/Kconfig +2 -2
@@ -14,7 +14,7 @@ config TEGRA_BPMP_THERMAL tristate "Tegra BPMP thermal sensing" depends on TEGRA_BPMP || COMPILE_TEST help - Enable this option for support for sensing system temperature of NVIDIA - Tegra systems-on-chip with the BPMP coprocessor (Tegra186). + Enable this option for support for sensing system temperature of NVIDIA + Tegra systems-on-chip with the BPMP coprocessor (Tegra186). endmenu
Signature · 1 line
1.9.1
PATCH 21/114 drivers: scsi: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/scsi/Kconfig | 63 +++++++++++++++++++++---------------------- drivers/scsi/pcmcia/Kconfig | 2 +- drivers/scsi/qedf/Kconfig | 8 +++--- drivers/scsi/smartpqi/Kconfig | 16 +++++------ 4 files changed, 44 insertions(+), 45 deletions(-)
drivers/scsi/Kconfig +31 -32
@@ -1,9 +1,9 @@ menu "SCSI device support" config SCSI_MOD - tristate - default y if SCSI=n || SCSI=y - default m if SCSI=m + tristate + default y if SCSI=n || SCSI=y + default m if SCSI=m config RAID_ATTRS tristate "RAID Transport Class"
@@ -47,7 +47,7 @@ config SCSI_ESP_PIO config SCSI_NETLINK bool - default n + default n depends on NET config SCSI_PROC_FS
@@ -307,25 +307,25 @@ config ISCSI_TCP select CRYPTO_CRC32C select SCSI_ISCSI_ATTRS help - The iSCSI Driver provides a host with the ability to access storage - through an IP network. The driver uses the iSCSI protocol to transport - SCSI requests and responses over a TCP/IP network between the host - (the "initiator") and "targets". Architecturally, the iSCSI driver - combines with the host's TCP/IP stack, network drivers, and Network - Interface Card (NIC) to provide the same functions as a SCSI or a - Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA). + The iSCSI Driver provides a host with the ability to access storage + through an IP network. The driver uses the iSCSI protocol to transport + SCSI requests and responses over a TCP/IP network between the host + (the "initiator") and "targets". Architecturally, the iSCSI driver + combines with the host's TCP/IP stack, network drivers, and Network + Interface Card (NIC) to provide the same functions as a SCSI or a + Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA). - To compile this driver as a module, choose M here: the - module will be called iscsi_tcp. + To compile this driver as a module, choose M here: the + module will be called iscsi_tcp. - The userspace component needed to initialize the driver, documentation, - and sample configuration files can be found here: + The userspace component needed to initialize the driver, documentation, + and sample configuration files can be found here: - http://open-iscsi.org + http://open-iscsi.org config ISCSI_BOOT_SYSFS tristate "iSCSI Boot Sysfs Interface" - default n + default n help This option enables support for exposing iSCSI boot information via sysfs to userspace. If you wish to export this information,
@@ -340,7 +340,7 @@ source "drivers/scsi/cxlflash/Kconfig" config SGIWD93_SCSI tristate "SGI WD93C93 SCSI Driver" depends on SGI_HAS_WD93 && SCSI - help + help If you have a Western Digital WD93 SCSI controller on an SGI MIPS system, say Y. Otherwise, say N.
@@ -455,7 +455,6 @@ config SCSI_AACRAID To compile this driver as a module, choose M here: the module will be called aacraid. - source "drivers/scsi/aic7xxx/Kconfig.aic7xxx" source "drivers/scsi/aic7xxx/Kconfig.aic79xx" source "drivers/scsi/aic94xx/Kconfig"
@@ -475,7 +474,7 @@ config SCSI_DPT_I2O tristate "Adaptec I2O RAID support " depends on SCSI && PCI && VIRT_TO_BUS help - This driver supports all of Adaptec's I2O based RAID controllers as + This driver supports all of Adaptec's I2O based RAID controllers as well as the DPT SmartRaid V cards. This is an Adaptec maintained driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
@@ -669,7 +668,7 @@ config SCSI_GDTH ---help--- Formerly called GDT SCSI Disk Array Controller Support. - This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) + This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) manufactured by Intel Corporation/ICP vortex GmbH. It is documented in the kernel source in <file:drivers/scsi/gdth.c> and <file:drivers/scsi/gdth.h>.
@@ -1152,8 +1151,8 @@ config SCSI_LPFC depends on NVME_FC || NVME_FC=n select CRC_T10DIF ---help--- - This lpfc driver supports the Emulex LightPulse - Family of Fibre Channel PCI host adapters. + This lpfc driver supports the Emulex LightPulse + Family of Fibre Channel PCI host adapters. config SCSI_LPFC_DEBUG_FS bool "Emulex LightPulse Fibre Channel debugfs Support"
@@ -1466,14 +1465,14 @@ config ZFCP depends on S390 && QDIO && SCSI depends on SCSI_FC_ATTRS help - If you want to access SCSI devices attached to your IBM eServer - zSeries by means of Fibre Channel interfaces say Y. - For details please refer to the documentation provided by IBM at - <http://oss.software.ibm.com/developerworks/opensource/linux390> + If you want to access SCSI devices attached to your IBM eServer + zSeries by means of Fibre Channel interfaces say Y. + For details please refer to the documentation provided by IBM at + <http://oss.software.ibm.com/developerworks/opensource/linux390> - This driver is also available as a module. This module will be - called zfcp. If you want to compile it as a module, say M here - and read <file:Documentation/kbuild/modules.txt>. + This driver is also available as a module. This module will be + called zfcp. If you want to compile it as a module, say M here + and read <file:Documentation/kbuild/modules.txt>. config SCSI_PMCRAID tristate "PMC SIERRA Linux MaxRAID adapter support"
@@ -1504,8 +1503,8 @@ config SCSI_VIRTIO tristate "virtio-scsi support" depends on VIRTIO help - This is the virtual HBA driver for virtio. If the kernel will - be used in a virtual machine, say Y or M. + This is the virtual HBA driver for virtio. If the kernel will + be used in a virtual machine, say Y or M. source "drivers/scsi/csiostor/Kconfig"
drivers/scsi/pcmcia/Kconfig +1 -1
@@ -32,7 +32,7 @@ config PCMCIA_NINJA_SCSI NinjaSCSI-3: (version string: "WBT","NinjaSCSI-3","R1.0") IO-DATA PCSC-FP ALPHA DATA AD-PCS201 - CyQ've SFC-201 + CyQ've SFC-201 LOGITECH LPM-SCSI2E Pioneer PCR-PR24's card I-O DATA CDPS-PX24's card (PCSC-F)
drivers/scsi/qedf/Kconfig +4 -4
@@ -2,10 +2,10 @@ config QEDF tristate "QLogic QEDF 25/40/100Gb FCoE Initiator Driver Support" depends on PCI && SCSI depends on QED - depends on LIBFC - depends on LIBFCOE + depends on LIBFC + depends on LIBFCOE select QED_LL2 select QED_FCOE ---help--- - This driver supports FCoE offload for the QLogic FastLinQ - 41000 Series Converged Network Adapters. + This driver supports FCoE offload for the QLogic FastLinQ + 41000 Series Converged Network Adapters.
drivers/scsi/smartpqi/Kconfig +8 -8
@@ -41,14 +41,14 @@ config SCSI_SMARTPQI select SCSI_SAS_ATTRS select RAID_ATTRS ---help--- - This driver supports Microsemi PQI controllers. + This driver supports Microsemi PQI controllers. - <http://www.microsemi.com> + <http://www.microsemi.com> - To compile this driver as a module, choose M here: the - module will be called smartpqi. + To compile this driver as a module, choose M here: the + module will be called smartpqi. - Note: the aacraid driver will not manage a smartpqi - controller. You need to enable smartpqi for smartpqi - controllers. For more information, please see - Documentation/scsi/smartpqi.txt + Note: the aacraid driver will not manage a smartpqi + controller. You need to enable smartpqi for smartpqi + controllers. For more information, please see + Documentation/scsi/smartpqi.txt
Signature · 1 line
1.9.1
PATCH 22/114 security: keys: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- security/keys/Kconfig | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-)
security/keys/Kconfig +11 -11
@@ -90,14 +90,14 @@ config ENCRYPTED_KEYS If you are unsure as to whether this is required, answer N. config KEY_DH_OPERATIONS - bool "Diffie-Hellman operations on retained keys" - depends on KEYS - select CRYPTO - select CRYPTO_HASH - select CRYPTO_DH - help - This option provides support for calculating Diffie-Hellman - public keys and shared secrets using values stored as keys - in the kernel. - - If you are unsure as to whether this is required, answer N. + bool "Diffie-Hellman operations on retained keys" + depends on KEYS + select CRYPTO + select CRYPTO_HASH + select CRYPTO_DH + help + This option provides support for calculating Diffie-Hellman + public keys and shared secrets using values stored as keys + in the kernel. + + If you are unsure as to whether this is required, answer N.
Signature · 1 line
1.9.1
PATCH 23/114 drivers: video: fbdev: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/video/fbdev/Kconfig | 288 +++++++++++----------- drivers/video/fbdev/mmp/Kconfig | 6 +- drivers/video/fbdev/omap/Kconfig | 20 +- drivers/video/fbdev/omap2/omapfb/Kconfig | 18 +- drivers/video/fbdev/omap2/omapfb/displays/Kconfig | 40 +-- drivers/video/fbdev/omap2/omapfb/dss/Kconfig | 6 +- 6 files changed, 188 insertions(+), 190 deletions(-)
drivers/video/fbdev/Kconfig +144 -144
@@ -45,25 +45,25 @@ menuconfig FB device-aware may cause unexpected results. If unsure, say N. config FIRMWARE_EDID - bool "Enable firmware EDID" - depends on FB - ---help--- - This enables access to the EDID transferred from the firmware. - On the i386, this is from the Video BIOS. Enable this if DDC/I2C - transfers do not work for your driver and if you are using - nvidiafb, i810fb or savagefb. - - In general, choosing Y for this option is safe. If you - experience extremely long delays while booting before you get - something on your display, try setting this to N. Matrox cards in - combination with certain motherboards and monitors are known to - suffer from this problem. + bool "Enable firmware EDID" + depends on FB + ---help--- + This enables access to the EDID transferred from the firmware. + On the i386, this is from the Video BIOS. Enable this if DDC/I2C + transfers do not work for your driver and if you are using + nvidiafb, i810fb or savagefb. + + In general, choosing Y for this option is safe. If you + experience extremely long delays while booting before you get + something on your display, try setting this to N. Matrox cards in + combination with certain motherboards and monitors are known to + suffer from this problem. config FB_DDC - tristate - depends on FB - select I2C_ALGOBIT - select I2C + tristate + depends on FB + select I2C_ALGOBIT + select I2C config FB_BOOT_VESA_SUPPORT bool
@@ -160,8 +160,8 @@ config FB_LITTLE_ENDIAN endchoice config FB_SYS_FOPS - tristate - depends on FB + tristate + depends on FB config FB_DEFERRED_IO bool
@@ -180,8 +180,8 @@ config FB_SVGALIB cards. config FB_MACMODES - tristate - depends on FB + tristate + depends on FB config FB_BACKLIGHT tristate
@@ -190,31 +190,31 @@ config FB_BACKLIGHT select BACKLIGHT_CLASS_DEVICE config FB_MODE_HELPERS - bool "Enable Video Mode Handling Helpers" - depends on FB + bool "Enable Video Mode Handling Helpers" + depends on FB ---help--- This enables functions for handling video modes using the Generalized Timing Formula and the EDID parser. A few drivers rely - on this feature such as the radeonfb, rivafb, and the i810fb. If + on this feature such as the radeonfb, rivafb, and the i810fb. If your driver does not take advantage of this feature, choosing Y will just increase the kernel size by about 5K. config FB_TILEBLITTING - bool "Enable Tile Blitting Support" - depends on FB - ---help--- - This enables tile blitting. Tile blitting is a drawing technique - where the screen is divided into rectangular sections (tiles), whereas - the standard blitting divides the screen into pixels. Because the - default drawing element is a tile, drawing functions will be passed - parameters in terms of number of tiles instead of number of pixels. - For example, to draw a single character, instead of using bitmaps, - an index to an array of bitmaps will be used. To clear or move a - rectangular section of a screen, the rectangle will be described in - terms of number of tiles in the x- and y-axis. - - This is particularly important to one driver, matroxfb. If - unsure, say N. + bool "Enable Tile Blitting Support" + depends on FB + ---help--- + This enables tile blitting. Tile blitting is a drawing technique + where the screen is divided into rectangular sections (tiles), whereas + the standard blitting divides the screen into pixels. Because the + default drawing element is a tile, drawing functions will be passed + parameters in terms of number of tiles instead of number of pixels. + For example, to draw a single character, instead of using bitmaps, + an index to an array of bitmaps will be used. To clear or move a + rectangular section of a screen, the rectangle will be described in + terms of number of tiles in the x- and y-axis. + + This is particularly important to one driver, matroxfb. If + unsure, say N. comment "Frame buffer hardware drivers" depends on FB
@@ -226,7 +226,7 @@ config FB_GRVGA select FB_CFB_COPYAREA select FB_CFB_IMAGEBLIT ---help--- - This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler. + This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler. config FB_CIRRUS tristate "Cirrus Logic support"
@@ -655,17 +655,17 @@ config FB_EFI using the EFI framebuffer as your console. config FB_N411 - tristate "N411 Apollo/Hecuba devkit support" - depends on FB && X86 && MMU - select FB_SYS_FILLRECT - select FB_SYS_COPYAREA - select FB_SYS_IMAGEBLIT - select FB_SYS_FOPS - select FB_DEFERRED_IO - select FB_HECUBA - help - This enables support for the Apollo display controller in its - Hecuba form using the n411 devkit. + tristate "N411 Apollo/Hecuba devkit support" + depends on FB && X86 && MMU + select FB_SYS_FILLRECT + select FB_SYS_COPYAREA + select FB_SYS_IMAGEBLIT + select FB_SYS_FOPS + select FB_DEFERRED_IO + select FB_HECUBA + help + This enables support for the Apollo display controller in its + Hecuba form using the n411 devkit. config FB_HGA tristate "Hercules mono graphics support"
@@ -685,7 +685,7 @@ config FB_GBE select FB_CFB_FILLRECT select FB_CFB_COPYAREA select FB_CFB_IMAGEBLIT - help + help This is the frame buffer device driver for SGI Graphics Backend. This chip is used in SGI O2 and Visual Workstation 320/540.
@@ -897,10 +897,10 @@ config FB_NVIDIA module will be called nvidiafb. config FB_NVIDIA_I2C - bool "Enable DDC Support" - depends on FB_NVIDIA - select FB_DDC - help + bool "Enable DDC Support" + depends on FB_NVIDIA + select FB_DDC + help This enables I2C support for nVidia Chipsets. This is used only for getting EDID information from the attached display allowing for robust video mode handling and switching.
@@ -943,10 +943,10 @@ config FB_RIVA module will be called rivafb. config FB_RIVA_I2C - bool "Enable DDC Support" - depends on FB_RIVA - select FB_DDC - help + bool "Enable DDC Support" + depends on FB_RIVA + select FB_DDC + help This enables I2C support for nVidia Chipsets. This is used only for getting EDID information from the attached display allowing for robust video mode handling and switching.
@@ -991,37 +991,37 @@ config FB_I810 select FB_CFB_IMAGEBLIT select VGASTATE help - This driver supports the on-board graphics built in to the Intel 810 - and 815 chipsets. Say Y if you have and plan to use such a board. + This driver supports the on-board graphics built in to the Intel 810 + and 815 chipsets. Say Y if you have and plan to use such a board. - To compile this driver as a module, choose M here: the + To compile this driver as a module, choose M here: the module will be called i810fb. - For more information, please read + For more information, please read <file:Documentation/fb/intel810.txt> config FB_I810_GTF bool "use VESA Generalized Timing Formula" depends on FB_I810 help - If you say Y, then the VESA standard, Generalized Timing Formula - or GTF, will be used to calculate the required video timing values - per video mode. Since the GTF allows nondiscrete timings - (nondiscrete being a range of values as opposed to discrete being a - set of values), you'll be able to use any combination of horizontal + If you say Y, then the VESA standard, Generalized Timing Formula + or GTF, will be used to calculate the required video timing values + per video mode. Since the GTF allows nondiscrete timings + (nondiscrete being a range of values as opposed to discrete being a + set of values), you'll be able to use any combination of horizontal and vertical resolutions, and vertical refresh rates without having to specify your own timing parameters. This is especially useful - to maximize the performance of an aging display, or if you just - have a display with nonstandard dimensions. A VESA compliant + to maximize the performance of an aging display, or if you just + have a display with nonstandard dimensions. A VESA compliant monitor is recommended, but can still work with non-compliant ones. - If you need or want this, then select this option. The timings may - not be compliant with Intel's recommended values. Use at your own + If you need or want this, then select this option. The timings may + not be compliant with Intel's recommended values. Use at your own risk. - If you say N, the driver will revert to discrete video timings + If you say N, the driver will revert to discrete video timings using a set recommended by Intel in their documentation. - - If unsure, say N. + + If unsure, say N. config FB_I810_I2C bool "Enable DDC Support"
@@ -1060,8 +1060,8 @@ config FB_INTEL depends on !DRM_I915 help This driver supports the on-board graphics built in to the Intel - 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets. - Say Y if you have and plan to use such a board. + 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets. + Say Y if you have and plan to use such a board. To make FB_INTEL=Y work you need to say AGP_INTEL=y too.
@@ -1142,10 +1142,10 @@ config FB_MATROX_G G450/G550 secondary head and digital output are supported without additional modules. - The driver starts in monitor mode. You must use the matroxset tool - (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to - swap primary and secondary head outputs, or to change output mode. - Secondary head driver always start in 640x480 resolution and you + The driver starts in monitor mode. You must use the matroxset tool + (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to + swap primary and secondary head outputs, or to change output mode. + Secondary head driver always start in 640x480 resolution and you must use fbset to change it. Do not forget that second head supports only 16 and 32 bpp
@@ -1228,7 +1228,7 @@ config FB_RADEON_I2C select FB_DDC default y help - Say Y here if you want DDC/I2C support for your Radeon board. + Say Y here if you want DDC/I2C support for your Radeon board. config FB_RADEON_BACKLIGHT bool "Support for backlight control"
@@ -1357,10 +1357,10 @@ config FB_SAVAGE will be called savagefb. config FB_SAVAGE_I2C - bool "Enable DDC2 Support" - depends on FB_SAVAGE - select FB_DDC - help + bool "Enable DDC2 Support" + depends on FB_SAVAGE + select FB_DDC + help This enables I2C support for S3 Savage Chipsets. This is used only for getting EDID information from the attached display allowing for robust video mode handling and switching.
@@ -1370,12 +1370,12 @@ config FB_SAVAGE_I2C here. config FB_SAVAGE_ACCEL - bool "Enable Console Acceleration" - depends on FB_SAVAGE - help - This option will compile in console acceleration support. If - the resulting framebuffer console has bothersome glitches, then - choose N here. + bool "Enable Console Acceleration" + depends on FB_SAVAGE + help + This option will compile in console acceleration support. If + the resulting framebuffer console has bothersome glitches, then + choose N here. config FB_SIS tristate "SiS/XGI display support"
@@ -1408,17 +1408,17 @@ config FB_SIS_315 as XGI V3XT, V5, V8 and Z7. config FB_VIA - tristate "VIA UniChrome (Pro) and Chrome9 display support" - depends on FB && PCI && GPIOLIB && I2C && (X86 || COMPILE_TEST) - select FB_CFB_FILLRECT - select FB_CFB_COPYAREA - select FB_CFB_IMAGEBLIT - select I2C_ALGOBIT - help + tristate "VIA UniChrome (Pro) and Chrome9 display support" + depends on FB && PCI && GPIOLIB && I2C && (X86 || COMPILE_TEST) + select FB_CFB_FILLRECT + select FB_CFB_COPYAREA + select FB_CFB_IMAGEBLIT + select I2C_ALGOBIT + help This is the frame buffer device driver for Graphics chips of VIA UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/ CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896 - /P4M900,VX800) + /P4M900,VX800) Say Y if you have a VIA UniChrome graphics board. To compile this driver as a module, choose M here: the
@@ -1455,7 +1455,7 @@ config FB_NEOMAGIC select VGASTATE help This driver supports notebooks with NeoMagic PCI chips. - Say Y if you have such a graphics card. + Say Y if you have such a graphics card. To compile this driver as a module, choose M here: the module will be called neofb.
@@ -1510,7 +1510,7 @@ config FB_VOODOO1 select FB_CFB_COPYAREA select FB_CFB_IMAGEBLIT ---help--- - Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or + Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or Voodoo2 (cvg) based graphics card. To compile this driver as a module, choose M here: the
@@ -1679,9 +1679,9 @@ config FB_HIT config FB_PMAG_AA tristate "PMAG-AA TURBOchannel framebuffer support" depends on FB && TC - select FB_CFB_FILLRECT - select FB_CFB_COPYAREA - select FB_CFB_IMAGEBLIT + select FB_CFB_FILLRECT + select FB_CFB_COPYAREA + select FB_CFB_IMAGEBLIT help Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1) used mainly in the MIPS-based DECstation series.
@@ -1689,9 +1689,9 @@ config FB_PMAG_AA config FB_PMAG_BA tristate "PMAG-BA TURBOchannel framebuffer support" depends on FB && TC - select FB_CFB_FILLRECT - select FB_CFB_COPYAREA - select FB_CFB_IMAGEBLIT + select FB_CFB_FILLRECT + select FB_CFB_COPYAREA + select FB_CFB_IMAGEBLIT help Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8) used mainly in the MIPS-based DECstation series.
@@ -1699,9 +1699,9 @@ config FB_PMAG_BA config FB_PMAGB_B tristate "PMAGB-B TURBOchannel framebuffer support" depends on FB && TC - select FB_CFB_FILLRECT - select FB_CFB_COPYAREA - select FB_CFB_IMAGEBLIT + select FB_CFB_FILLRECT + select FB_CFB_COPYAREA + select FB_CFB_IMAGEBLIT help Support for the PMAGB-B TURBOchannel framebuffer card used mainly in the MIPS-based DECstation series. The card is currently only
@@ -1710,9 +1710,9 @@ config FB_PMAGB_B config FB_MAXINE bool "Maxine (Personal DECstation) onboard framebuffer support" depends on (FB = y) && MACH_DECSTATION - select FB_CFB_FILLRECT - select FB_CFB_COPYAREA - select FB_CFB_IMAGEBLIT + select FB_CFB_FILLRECT + select FB_CFB_COPYAREA + select FB_CFB_IMAGEBLIT help Support for the onboard framebuffer (1024x768x8) in the Personal DECstation series (Personal DECstation 5000/20, /25, /33, /50,
@@ -1721,9 +1721,9 @@ config FB_MAXINE config FB_G364 bool "G364 frame buffer support" depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700) - select FB_CFB_FILLRECT - select FB_CFB_COPYAREA - select FB_CFB_IMAGEBLIT + select FB_CFB_FILLRECT + select FB_CFB_COPYAREA + select FB_CFB_IMAGEBLIT help The G364 driver is the framebuffer used in MIPS Magnum 4000 and Olivetti M700-10 systems.
@@ -1731,9 +1731,9 @@ config FB_G364 config FB_68328 bool "Motorola 68328 native frame buffer support" depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328) - select FB_CFB_FILLRECT - select FB_CFB_COPYAREA - select FB_CFB_IMAGEBLIT + select FB_CFB_FILLRECT + select FB_CFB_COPYAREA + select FB_CFB_IMAGEBLIT help Say Y here if you want to support the built-in frame buffer of the Motorola 68328 CPU family.
@@ -1812,13 +1812,13 @@ config FB_MBX Accelerator config FB_MBX_DEBUG - bool "Enable debugging info via debugfs" - depends on FB_MBX && DEBUG_FS - ---help--- - Enable this if you want debugging information using the debug - filesystem (debugfs) + bool "Enable debugging info via debugfs" + depends on FB_MBX && DEBUG_FS + ---help--- + Enable this if you want debugging information using the debug + filesystem (debugfs) - If unsure, say N. + If unsure, say N. config FB_FSL_DIU tristate "Freescale DIU framebuffer support"
@@ -1834,9 +1834,9 @@ config FB_FSL_DIU config FB_W100 tristate "W100 frame buffer support" depends on FB && ARCH_PXA - select FB_CFB_FILLRECT - select FB_CFB_COPYAREA - select FB_CFB_IMAGEBLIT + select FB_CFB_FILLRECT + select FB_CFB_COPYAREA + select FB_CFB_IMAGEBLIT ---help--- Frame buffer driver for the w100 as found on the Sharp SL-Cxx series. It can also drive the w3220 chip found on iPAQ hx4700.
@@ -1901,10 +1901,10 @@ config FB_S3C Currently the support is only for the S3C6400 and S3C6410 SoCs. config FB_S3C_DEBUG_REGWRITE - bool "Debug register writes" - depends on FB_S3C - ---help--- - Show all register writes via pr_debug() + bool "Debug register writes" + depends on FB_S3C + ---help--- + Show all register writes via pr_debug() config FB_S3C2410 tristate "S3C2410 LCD framebuffer support"
@@ -1930,18 +1930,18 @@ config FB_S3C2410_DEBUG through sysfs config FB_NUC900 - tristate "NUC900 LCD framebuffer support" - depends on FB && ARCH_W90X900 - select FB_CFB_FILLRECT - select FB_CFB_COPYAREA - select FB_CFB_IMAGEBLIT - ---help--- - Frame buffer driver for the built-in LCD controller in the Nuvoton - NUC900 processor + tristate "NUC900 LCD framebuffer support" + depends on FB && ARCH_W90X900 + select FB_CFB_FILLRECT + select FB_CFB_COPYAREA + select FB_CFB_IMAGEBLIT + ---help--- + Frame buffer driver for the built-in LCD controller in the Nuvoton + NUC900 processor config GPM1040A0_320X240 - bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD" - depends on FB_NUC900 + bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD" + depends on FB_NUC900 config FB_SM501 tristate "Silicon Motion SM501 framebuffer support"
drivers/video/fbdev/mmp/Kconfig +3 -3
@@ -1,7 +1,7 @@ menuconfig MMP_DISP - tristate "Marvell MMP Display Subsystem support" - depends on CPU_PXA910 || CPU_MMP2 - help + tristate "Marvell MMP Display Subsystem support" + depends on CPU_PXA910 || CPU_MMP2 + help Marvell Display Subsystem support. if MMP_DISP
drivers/video/fbdev/omap/Kconfig +9 -11
@@ -6,7 +6,7 @@ config FB_OMAP select FB_CFB_COPYAREA select FB_CFB_IMAGEBLIT help - Frame buffer driver for OMAP based boards. + Frame buffer driver for OMAP based boards. config FB_OMAP_LCDC_EXTERNAL bool "External LCD controller support"
@@ -49,13 +49,11 @@ config FB_OMAP_LCD_H3 H3 board. config FB_OMAP_DMA_TUNE - bool "Set DMA SDRAM access priority high" - depends on FB_OMAP - help - On systems in which video memory is in system memory - (SDRAM) this will speed up graphics DMA operations. - If you have such a system and want to use rotation - answer yes. Answer no if you have a dedicated video - memory, or don't use any of the accelerated features. - - + bool "Set DMA SDRAM access priority high" + depends on FB_OMAP + help + On systems in which video memory is in system memory + (SDRAM) this will speed up graphics DMA operations. + If you have such a system and want to use rotation + answer yes. Answer no if you have a dedicated video + memory, or don't use any of the accelerated features.
drivers/video/fbdev/omap2/omapfb/Kconfig +9 -9
@@ -2,23 +2,23 @@ config OMAP2_VRFB bool menuconfig FB_OMAP2 - tristate "OMAP2+ frame buffer support" - depends on FB - depends on DRM_OMAP = n + tristate "OMAP2+ frame buffer support" + depends on FB + depends on DRM_OMAP = n depends on GPIOLIB - select FB_OMAP2_DSS + select FB_OMAP2_DSS select OMAP2_VRFB if ARCH_OMAP2 || ARCH_OMAP3 - select FB_CFB_FILLRECT - select FB_CFB_COPYAREA - select FB_CFB_IMAGEBLIT - help + select FB_CFB_FILLRECT + select FB_CFB_COPYAREA + select FB_CFB_IMAGEBLIT + help Frame buffer driver for OMAP2+ based boards. if FB_OMAP2 config FB_OMAP2_DEBUG_SUPPORT - bool "Debug support for OMAP2+ FB" + bool "Debug support for OMAP2+ FB" default y depends on FB_OMAP2 help
drivers/video/fbdev/omap2/omapfb/displays/Kconfig +20 -20
@@ -1,5 +1,5 @@ menu "OMAPFB Panel and Encoder Drivers" - depends on FB_OMAP2_DSS + depends on FB_OMAP2_DSS config FB_OMAP2_ENCODER_OPA362 tristate "OPA362 external analog amplifier"
@@ -8,29 +8,29 @@ config FB_OMAP2_ENCODER_OPA362 through a GPIO. config FB_OMAP2_ENCODER_TFP410 - tristate "TFP410 DPI to DVI Encoder" + tristate "TFP410 DPI to DVI Encoder" help Driver for TFP410 DPI to DVI encoder. config FB_OMAP2_ENCODER_TPD12S015 - tristate "TPD12S015 HDMI ESD protection and level shifter" + tristate "TPD12S015 HDMI ESD protection and level shifter" help Driver for TPD12S015, which offers HDMI ESD protection and level shifting. config FB_OMAP2_CONNECTOR_DVI - tristate "DVI Connector" + tristate "DVI Connector" depends on I2C help Driver for a generic DVI connector. config FB_OMAP2_CONNECTOR_HDMI - tristate "HDMI Connector" + tristate "HDMI Connector" help Driver for a generic HDMI connector. config FB_OMAP2_CONNECTOR_ANALOG_TV - tristate "Analog TV Connector" + tristate "Analog TV Connector" help Driver for a generic analog TV connector.
@@ -58,29 +58,29 @@ config FB_OMAP2_PANEL_LGPHILIPS_LB035Q02 LCD Panel used on the Gumstix Overo Palo35 config FB_OMAP2_PANEL_SHARP_LS037V7DW01 - tristate "Sharp LS037V7DW01 LCD Panel" - depends on BACKLIGHT_CLASS_DEVICE - help - LCD Panel used in TI's SDP3430 and EVM boards + tristate "Sharp LS037V7DW01 LCD Panel" + depends on BACKLIGHT_CLASS_DEVICE + help + LCD Panel used in TI's SDP3430 and EVM boards config FB_OMAP2_PANEL_TPO_TD028TTEC1 - tristate "TPO TD028TTEC1 LCD Panel" - depends on SPI - help - LCD panel used in Openmoko. + tristate "TPO TD028TTEC1 LCD Panel" + depends on SPI + help + LCD panel used in Openmoko. config FB_OMAP2_PANEL_TPO_TD043MTEA1 - tristate "TPO TD043MTEA1 LCD Panel" - depends on SPI - help - LCD Panel used in OMAP3 Pandora + tristate "TPO TD043MTEA1 LCD Panel" + depends on SPI + help + LCD Panel used in OMAP3 Pandora config FB_OMAP2_PANEL_NEC_NL8048HL11 tristate "NEC NL8048HL11 Panel" depends on SPI depends on BACKLIGHT_CLASS_DEVICE help - This NEC NL8048HL11 panel is TFT LCD used in the - Zoom2/3/3630 sdp boards. + This NEC NL8048HL11 panel is TFT LCD used in the + Zoom2/3/3630 sdp boards. endmenu
drivers/video/fbdev/omap2/omapfb/dss/Kconfig +3 -3
@@ -3,7 +3,7 @@ config FB_OMAP2_DSS_INIT bool config FB_OMAP2_DSS - tristate + tristate select VIDEOMODE_HELPERS select FB_OMAP2_DSS_INIT select HDMI
@@ -53,7 +53,7 @@ config FB_OMAP2_DSS_RFBI config FB_OMAP2_DSS_VENC bool "VENC support" - default y + default y help OMAP Video Encoder support for S-Video and composite TV-out.
@@ -62,7 +62,7 @@ config FB_OMAP2_DSS_HDMI_COMMON config FB_OMAP4_DSS_HDMI bool "HDMI support for OMAP4" - default y + default y select FB_OMAP2_DSS_HDMI_COMMON help HDMI support for OMAP4 based SoCs.
Signature · 1 line
1.9.1
PATCH 24/114 s390: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/s390/Kconfig | 2 +- drivers/s390/block/Kconfig | 2 +- drivers/s390/char/Kconfig | 15 +++++++-------- drivers/s390/net/Kconfig | 8 ++++---- 4 files changed, 13 insertions(+), 14 deletions(-)
arch/s390/Kconfig +1 -1
@@ -723,7 +723,7 @@ config PCI_NR_FUNCTIONS This allows you to specify the maximum number of PCI functions which this kernel will support. -endif # PCI +endif # PCI config HAS_IOMEM def_bool PCI
drivers/s390/block/Kconfig +1 -1
@@ -38,7 +38,7 @@ config DASD_PROFILE depends on DASD help Enable this option if you want to see profiling information - in /proc/dasd/statistics. + in /proc/dasd/statistics. config DASD_ECKD def_tristate y
drivers/s390/char/Kconfig +7 -8
@@ -91,14 +91,14 @@ config SCLP_ASYNC need this feature and intend to run your kernel in LPAR. config SCLP_ASYNC_ID - string "Component ID for Call Home" - depends on SCLP_ASYNC - default "000000000" - help - The Component ID for Call Home is used to identify the correct - problem reporting queue the call home records should be sent to. + string "Component ID for Call Home" + depends on SCLP_ASYNC + default "000000000" + help + The Component ID for Call Home is used to identify the correct + problem reporting queue the call home records should be sent to. - If your are unsure, please use the default value "000000000". + If your are unsure, please use the default value "000000000". config HMC_DRV def_tristate m
@@ -205,4 +205,3 @@ config S390_VMUR depends on S390 help Character device driver for z/VM reader, puncher and printer. -
drivers/s390/net/Kconfig +4 -4
@@ -7,10 +7,10 @@ config LCS prompt "Lan Channel Station Interface" depends on CCW && NETDEVICES && (ETHERNET || FDDI) help - Select this option if you want to use LCS networking on IBM System z. - This device driver supports FDDI (IEEE 802.7) and Ethernet. - To compile as a module, choose M. The module name is lcs. - If you do not know what it is, it's safe to choose Y. + Select this option if you want to use LCS networking on IBM System z. + This device driver supports FDDI (IEEE 802.7) and Ethernet. + To compile as a module, choose M. The module name is lcs. + If you do not know what it is, it's safe to choose Y. config CTCM def_tristate m
Signature · 1 line
1.9.1
PATCH 25/114 arch: sh: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/sh/Kconfig | 24 ++++++++++++------------ arch/sh/boards/Kconfig | 10 +++++----- arch/sh/mm/Kconfig | 6 +++--- 3 files changed, 20 insertions(+), 20 deletions(-)
arch/sh/Kconfig +12 -12
@@ -233,9 +233,9 @@ config ARCH_SHMOBILE select PM config CPU_HAS_PMU - depends on CPU_SH4 || CPU_SH4A - default y - bool + depends on CPU_SH4 || CPU_SH4A + default y + bool if SUPERH32
@@ -266,7 +266,7 @@ config CPU_SUBTYPE_SH7201 select CPU_SH2A select CPU_HAS_FPU select SYS_SUPPORTS_SH_MTU2 - + config CPU_SUBTYPE_SH7203 bool "Support SH7203 processor" select CPU_SH2A
@@ -549,7 +549,7 @@ endchoice endif source "arch/sh/mm/Kconfig" - + source "arch/sh/Kconfig.cpu" source "arch/sh/boards/Kconfig"
@@ -716,7 +716,7 @@ config GUSA This is the default implementation for both UP and non-ll/sc CPUs, and is used by the libc, amongst others. - For additional information, design information can be found + For additional information, design information can be found in <http://lc.linux.or.jp/lc2002/papers/niibe0919p.pdf>. This should only be disabled for special cases where alternate
@@ -848,12 +848,12 @@ config MAPLE bool "Maple Bus support" depends on SH_DREAMCAST help - The Maple Bus is SEGA's serial communication bus for peripherals - on the Dreamcast. Without this bus support you won't be able to - get your Dreamcast keyboard etc to work, so most users - probably want to say 'Y' here, unless you are only using the - Dreamcast with a serial line terminal or a remote network - connection. + The Maple Bus is SEGA's serial communication bus for peripherals + on the Dreamcast. Without this bus support you won't be able to + get your Dreamcast keyboard etc to work, so most users + probably want to say 'Y' here, unless you are only using the + Dreamcast with a serial line terminal or a remote network + connection. endmenu
arch/sh/boards/Kconfig +5 -5
@@ -39,7 +39,7 @@ config SH_SOLUTION_ENGINE select CPU_HAS_IPR_IRQ depends on CPU_SUBTYPE_SH7705 || CPU_SUBTYPE_SH7709 || CPU_SUBTYPE_SH7710 || \ CPU_SUBTYPE_SH7712 || CPU_SUBTYPE_SH7750 || CPU_SUBTYPE_SH7750S || \ - CPU_SUBTYPE_SH7750R + CPU_SUBTYPE_SH7750R help Select SolutionEngine if configuring for a Hitachi SH7705, SH7709, SH7710, SH7712, SH7750, SH7750S or SH7750R evaluation board.
@@ -97,7 +97,7 @@ config SH_7751_SOLUTION_ENGINE help Select 7751 SolutionEngine if configuring for a Hitachi SH7751 evaluation board. - + config SH_7780_SOLUTION_ENGINE bool "SolutionEngine7780" select SOLUTION_ENGINE
@@ -170,8 +170,8 @@ config SH_RSK CPU_SUBTYPE_SH7264 || CPU_SUBTYPE_SH7269 select REGULATOR_FIXED_VOLTAGE if REGULATOR help - Select this option if configuring for any of the RSK+ MCU - evaluation platforms. + Select this option if configuring for any of the RSK+ MCU + evaluation platforms. config SH_SDK7780 bool "SDK7780R3"
@@ -239,7 +239,7 @@ config SH_MIGOR select REGULATOR_FIXED_VOLTAGE if REGULATOR help Select Migo-R if configuring for the SH7722 Migo-R platform - by Renesas System Solutions Asia Pte. Ltd. + by Renesas System Solutions Asia Pte. Ltd. config SH_AP325RXA bool "AP-325RXA"
arch/sh/mm/Kconfig +3 -3
@@ -5,7 +5,7 @@ config QUICKLIST def_bool y config MMU - bool "Support for memory management hardware" + bool "Support for memory management hardware" depends on !CPU_SH2 default y help
@@ -154,8 +154,8 @@ config ARCH_MEMORY_PROBE depends on MEMORY_HOTPLUG config IOREMAP_FIXED - def_bool y - depends on X2TLB || SUPERH64 + def_bool y + depends on X2TLB || SUPERH64 config UNCACHED_MAPPING bool
Signature · 1 line
1.9.1
PATCH 26/114 arch: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/Kconfig | 94 ++++++++++++++++++++++++++++++------------------------------ 1 file changed, 47 insertions(+), 47 deletions(-)
arch/Kconfig +47 -47
@@ -69,30 +69,30 @@ config KPROBES If in doubt, say "N". config JUMP_LABEL - bool "Optimize very unlikely/likely branches" - depends on HAVE_ARCH_JUMP_LABEL - depends on CC_HAS_ASM_GOTO - help - This option enables a transparent branch optimization that - makes certain almost-always-true or almost-always-false branch - conditions even cheaper to execute within the kernel. - - Certain performance-sensitive kernel code, such as trace points, - scheduler functionality, networking code and KVM have such - branches and include support for this optimization technique. - - If it is detected that the compiler has support for "asm goto", - the kernel will compile such branches with just a nop - instruction. When the condition flag is toggled to true, the - nop will be converted to a jump instruction to execute the - conditional block of instructions. - - This technique lowers overhead and stress on the branch prediction - of the processor and generally makes the kernel faster. The update - of the condition is slower, but those are always very rare. - - ( On 32-bit x86, the necessary options added to the compiler - flags may increase the size of the kernel slightly. ) + bool "Optimize very unlikely/likely branches" + depends on HAVE_ARCH_JUMP_LABEL + depends on CC_HAS_ASM_GOTO + help + This option enables a transparent branch optimization that + makes certain almost-always-true or almost-always-false branch + conditions even cheaper to execute within the kernel. + + Certain performance-sensitive kernel code, such as trace points, + scheduler functionality, networking code and KVM have such + branches and include support for this optimization technique. + + If it is detected that the compiler has support for "asm goto", + the kernel will compile such branches with just a nop + instruction. When the condition flag is toggled to true, the + nop will be converted to a jump instruction to execute the + conditional block of instructions. + + This technique lowers overhead and stress on the branch prediction + of the processor and generally makes the kernel faster. The update + of the condition is slower, but those are always very rare. + + ( On 32-bit x86, the necessary options added to the compiler + flags may increase the size of the kernel slightly. ) config STATIC_KEYS_SELFTEST bool "Static key selftest"
@@ -110,9 +110,9 @@ config KPROBES_ON_FTRACE depends on KPROBES && HAVE_KPROBES_ON_FTRACE depends on DYNAMIC_FTRACE_WITH_REGS help - If function tracer is enabled and the arch supports full - passing of pt_regs to function tracing, then kprobes can - optimize on top of function tracing. + If function tracer is enabled and the arch supports full + passing of pt_regs to function tracing, then kprobes can + optimize on top of function tracing. config UPROBES def_bool n
@@ -164,23 +164,23 @@ config HAVE_EFFICIENT_UNALIGNED_ACCESS information on the topic of unaligned memory accesses. config ARCH_USE_BUILTIN_BSWAP - bool - help - Modern versions of GCC (since 4.4) have builtin functions - for handling byte-swapping. Using these, instead of the old - inline assembler that the architecture code provides in the - __arch_bswapXX() macros, allows the compiler to see what's - happening and offers more opportunity for optimisation. In - particular, the compiler will be able to combine the byteswap - with a nearby load or store and use load-and-swap or - store-and-swap instructions if the architecture has them. It - should almost *never* result in code which is worse than the - hand-coded assembler in <asm/swab.h>. But just in case it - does, the use of the builtins is optional. - - Any architecture with load-and-swap or store-and-swap - instructions should set this. And it shouldn't hurt to set it - on architectures that don't have such instructions. + bool + help + Modern versions of GCC (since 4.4) have builtin functions + for handling byte-swapping. Using these, instead of the old + inline assembler that the architecture code provides in the + __arch_bswapXX() macros, allows the compiler to see what's + happening and offers more opportunity for optimisation. In + particular, the compiler will be able to combine the byteswap + with a nearby load or store and use load-and-swap or + store-and-swap instructions if the architecture has them. It + should almost *never* result in code which is worse than the + hand-coded assembler in <asm/swab.h>. But just in case it + does, the use of the builtins is optional. + + Any architecture with load-and-swap or store-and-swap + instructions should set this. And it shouldn't hurt to set it + on architectures that don't have such instructions. config KRETPROBES def_bool y
@@ -234,10 +234,10 @@ config HAVE_DMA_CONTIGUOUS bool config GENERIC_SMP_IDLE_THREAD - bool + bool config GENERIC_IDLE_POLL_SETUP - bool + bool config ARCH_HAS_FORTIFY_SOURCE bool
@@ -251,7 +251,7 @@ config ARCH_HAS_SET_MEMORY # Select if arch init_task must go in the __init_task_data section config ARCH_TASK_STRUCT_ON_STACK - bool + bool # Select if arch has its private alloc_task_struct() function config ARCH_TASK_STRUCT_ALLOCATOR
Signature · 1 line
1.9.1
PATCH 27/114 virt: kvm: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- virt/kvm/Kconfig | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 deletions(-)
virt/kvm/Kconfig +20 -20
@@ -2,58 +2,58 @@ # KVM common configuration items and defaults config HAVE_KVM - bool + bool config HAVE_KVM_IRQCHIP - bool + bool config HAVE_KVM_IRQFD - bool + bool config HAVE_KVM_IRQ_ROUTING - bool + bool config HAVE_KVM_EVENTFD - bool - select EVENTFD + bool + select EVENTFD config KVM_MMIO - bool + bool config KVM_ASYNC_PF - bool + bool # Toggle to switch between direct notification and batch job config KVM_ASYNC_PF_SYNC - bool + bool config HAVE_KVM_MSI - bool + bool config HAVE_KVM_CPU_RELAX_INTERCEPT - bool + bool config KVM_VFIO - bool + bool config HAVE_KVM_ARCH_TLB_FLUSH_ALL - bool + bool config HAVE_KVM_INVALID_WAKEUPS - bool + bool config KVM_GENERIC_DIRTYLOG_READ_PROTECT - bool + bool config KVM_COMPAT - def_bool y - depends on KVM && COMPAT && !(S390 || ARM64) + def_bool y + depends on KVM && COMPAT && !(S390 || ARM64) config HAVE_KVM_IRQ_BYPASS - bool + bool config HAVE_KVM_VCPU_ASYNC_IOCTL - bool + bool config HAVE_KVM_VCPU_RUN_PID_CHANGE - bool + bool
Signature · 1 line
1.9.1
PATCH 28/114 arch: alpha: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/alpha/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/alpha/Kconfig +2 -2
@@ -550,7 +550,7 @@ config NR_CPUS default "4" if !ALPHA_GENERIC && !ALPHA_MARVEL help MARVEL support can handle a maximum of 32 CPUs, all the others - with working support have a maximum of 4 CPUs. + with working support have a maximum of 4 CPUs. config ARCH_DISCONTIGMEM_ENABLE bool "Discontiguous Memory Support"
@@ -662,7 +662,7 @@ choice endchoice config HZ - int + int default 32 if HZ_32 default 64 if HZ_64 default 128 if HZ_128
Signature · 1 line
1.9.1
PATCH 29/114 sound: drivers: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- sound/drivers/Kconfig | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-)
sound/drivers/Kconfig +13 -13
@@ -1,6 +1,6 @@ config SND_MPU401_UART - tristate - select SND_RAWMIDI + tristate + select SND_RAWMIDI config SND_OPL3_LIB tristate
@@ -42,7 +42,7 @@ menuconfig SND_DRIVERS default y help Support for generic sound devices. - + if SND_DRIVERS config SND_PCSP
@@ -89,16 +89,16 @@ config SND_DUMMY will be called snd-dummy. config SND_ALOOP - tristate "Generic loopback driver (PCM)" - select SND_PCM - help - Say 'Y' or 'M' to include support for the PCM loopback device. + tristate "Generic loopback driver (PCM)" + select SND_PCM + help + Say 'Y' or 'M' to include support for the PCM loopback device. This module returns played samples back to the user space using the standard ALSA PCM device. The devices are routed 0->1 and 1->0, where first number is the playback PCM device and second number is the capture device. Module creates two PCM devices and configured number of substreams (see the pcm_substreams module - parameter). + parameter). The loopback device allows time sychronization with an external timing source using the time shift universal control (+-20%
@@ -140,13 +140,13 @@ config SND_MTS64 depends on PARPORT select SND_RAWMIDI help - The ESI Miditerminal 4140 is a 4 In 4 Out MIDI Interface with - additional SMPTE Timecode capabilities for the parallel port. + The ESI Miditerminal 4140 is a 4 In 4 Out MIDI Interface with + additional SMPTE Timecode capabilities for the parallel port. Say 'Y' to include support for this device. - To compile this driver as a module, chose 'M' here: the module - will be called snd-mts64. + To compile this driver as a module, chose 'M' here: the module + will be called snd-mts64. config SND_SERIAL_U16550 tristate "UART16550 serial MIDI driver"
@@ -235,4 +235,4 @@ config SND_AC97_POWER_SAVE_DEFAULT See SND_AC97_POWER_SAVE for more details. -endif # SND_DRIVERS +endif # SND_DRIVERS
Signature · 1 line
1.9.1
PATCH 30/114 sound: oao: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- sound/aoa/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
sound/aoa/Kconfig +3 -3
@@ -3,8 +3,8 @@ menuconfig SND_AOA depends on PPC_PMAC select SND_PCM ---help--- - This option enables the new driver for the various - Apple Onboard Audio components. + This option enables the new driver for the various + Apple Onboard Audio components. if SND_AOA
@@ -14,4 +14,4 @@ source "sound/aoa/codecs/Kconfig" source "sound/aoa/soundbus/Kconfig" -endif # SND_AOA +endif # SND_AOA
Signature · 1 line
1.9.1
PATCH 31/114 secuirty: integrity: ima: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- security/integrity/ima/Kconfig | 64 +++++++++++++++++++++--------------------- 1 file changed, 32 insertions(+), 32 deletions(-)
security/integrity/ima/Kconfig +32 -32
@@ -34,12 +34,12 @@ config IMA_KEXEC depends on IMA && TCG_TPM && HAVE_IMA_KEXEC default n help - TPM PCRs are only reset on a hard reboot. In order to validate - a TPM's quote after a soft boot, the IMA measurement list of the - running kernel must be saved and restored on boot. + TPM PCRs are only reset on a hard reboot. In order to validate + a TPM's quote after a soft boot, the IMA measurement list of the + running kernel must be saved and restored on boot. - Depending on the IMA policy, the measurement list can grow to - be very large. + Depending on the IMA policy, the measurement list can grow to + be very large. config IMA_MEASURE_PCR_IDX int
@@ -91,10 +91,10 @@ choice default IMA_DEFAULT_HASH_SHA1 depends on IMA help - Select the default hash algorithm used for the measurement - list, integrity appraisal and audit log. The compiled default - hash algorithm can be overwritten using the kernel command - line 'ima_hash=' option. + Select the default hash algorithm used for the measurement + list, integrity appraisal and audit log. The compiled default + hash algorithm can be overwritten using the kernel command + line 'ima_hash=' option. config IMA_DEFAULT_HASH_SHA1 bool "SHA1 (default)"
@@ -138,9 +138,9 @@ config IMA_READ_POLICY default y if IMA_WRITE_POLICY default n if !IMA_WRITE_POLICY help - It is often useful to be able to read back the IMA policy. It is - even more important after introducing CONFIG_IMA_WRITE_POLICY. - This option allows the root user to see the current policy rules. + It is often useful to be able to read back the IMA policy. It is + even more important after introducing CONFIG_IMA_WRITE_POLICY. + This option allows the root user to see the current policy rules. config IMA_APPRAISE bool "Appraise integrity measurements"
@@ -158,12 +158,12 @@ config IMA_APPRAISE If unsure, say N. config IMA_ARCH_POLICY - bool "Enable loading an IMA architecture specific policy" - depends on KEXEC_VERIFY_SIG || IMA_APPRAISE && INTEGRITY_ASYMMETRIC_KEYS - default n - help - This option enables loading an IMA architecture specific policy - based on run time secure boot flags. + bool "Enable loading an IMA architecture specific policy" + depends on KEXEC_VERIFY_SIG || IMA_APPRAISE && INTEGRITY_ASYMMETRIC_KEYS + default n + help + This option enables loading an IMA architecture specific policy + based on run time secure boot flags. config IMA_APPRAISE_BUILD_POLICY bool "IMA build time configured policy rules"
@@ -238,10 +238,10 @@ config IMA_TRUSTED_KEYRING select INTEGRITY_TRUSTED_KEYRING default y help - This option requires that all keys added to the .ima - keyring be signed by a key on the system trusted keyring. + This option requires that all keys added to the .ima + keyring be signed by a key on the system trusted keyring. - This option is deprecated in favor of INTEGRITY_TRUSTED_KEYRING + This option is deprecated in favor of INTEGRITY_TRUSTED_KEYRING config IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY bool "Permit keys validly signed by a built-in or secondary CA cert (EXPERIMENTAL)"
@@ -266,32 +266,32 @@ config IMA_BLACKLIST_KEYRING depends on IMA_TRUSTED_KEYRING default n help - This option creates an IMA blacklist keyring, which contains all - revoked IMA keys. It is consulted before any other keyring. If - the search is successful the requested operation is rejected and - an error is returned to the caller. + This option creates an IMA blacklist keyring, which contains all + revoked IMA keys. It is consulted before any other keyring. If + the search is successful the requested operation is rejected and + an error is returned to the caller. config IMA_LOAD_X509 bool "Load X509 certificate onto the '.ima' trusted keyring" depends on IMA_TRUSTED_KEYRING default n help - File signature verification is based on the public keys - loaded on the .ima trusted keyring. These public keys are - X509 certificates signed by a trusted key on the - .system keyring. This option enables X509 certificate - loading from the kernel onto the '.ima' trusted keyring. + File signature verification is based on the public keys + loaded on the .ima trusted keyring. These public keys are + X509 certificates signed by a trusted key on the + .system keyring. This option enables X509 certificate + loading from the kernel onto the '.ima' trusted keyring. config IMA_X509_PATH string "IMA X509 certificate path" depends on IMA_LOAD_X509 default "/etc/keys/x509_ima.der" help - This option defines IMA X509 certificate path. + This option defines IMA X509 certificate path. config IMA_APPRAISE_SIGNED_INIT bool "Require signed user-space initialization" depends on IMA_LOAD_X509 default n help - This option requires user-space init to be signed. + This option requires user-space init to be signed.
Signature · 1 line
1.9.1
PATCH 32/114 sound: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- sound/arm/Kconfig | 2 +- sound/core/Kconfig | 28 +++++----- sound/firewire/Kconfig | 122 ++++++++++++++++++++--------------------- sound/hda/Kconfig | 4 +- sound/isa/Kconfig | 27 +++++---- sound/mips/Kconfig | 15 +++-- sound/parisc/Kconfig | 2 +- sound/pci/Kconfig | 4 +- sound/pcmcia/Kconfig | 3 +- sound/ppc/Kconfig | 2 +- sound/sh/Kconfig | 3 +- sound/soc/Kconfig | 5 +- sound/soc/amd/Kconfig | 8 +-- sound/soc/cirrus/Kconfig | 14 ++--- sound/soc/codecs/Kconfig | 60 ++++++++++---------- sound/soc/dwc/Kconfig | 15 +++-- sound/soc/fsl/Kconfig | 8 +-- sound/soc/generic/Kconfig | 2 +- sound/soc/intel/Kconfig | 2 +- sound/soc/intel/boards/Kconfig | 82 +++++++++++++-------------- sound/soc/jz4740/Kconfig | 2 +- sound/soc/mxs/Kconfig | 3 +- sound/soc/pxa/Kconfig | 29 +++++----- sound/soc/samsung/Kconfig | 8 +-- sound/soc/zte/Kconfig | 12 ++-- sound/sparc/Kconfig | 2 +- sound/spi/Kconfig | 3 +- sound/usb/Kconfig | 47 ++++++++-------- sound/x86/Kconfig | 4 +- 29 files changed, 254 insertions(+), 264 deletions(-)
sound/arm/Kconfig +1 -1
@@ -27,7 +27,7 @@ config SND_PXA2XX_AC97 Say Y or M if you want to support any AC97 codec attached to the PXA2xx AC97 interface. -endif # SND_ARM +endif # SND_ARM config SND_PXA2XX_LIB tristate
sound/core/Kconfig +14 -14
@@ -71,11 +71,11 @@ config SND_PCM_OSS config SND_PCM_OSS_PLUGINS bool "OSS PCM (digital audio) API - Include plugin system" depends on SND_PCM_OSS - default y + default y help - If you disable this option, the ALSA's OSS PCM API will not - support conversion of channels, formats and rates. It will - behave like most of new OSS/Free drivers in 2.4/2.6 kernels. + If you disable this option, the ALSA's OSS PCM API will not + support conversion of channels, formats and rates. It will + behave like most of new OSS/Free drivers in 2.4/2.6 kernels. config SND_PCM_TIMER bool "PCM timer interface" if EXPERT
@@ -127,13 +127,13 @@ config SND_SUPPORT_OLD_API or older). config SND_PROC_FS - bool "Sound Proc FS Support" if EXPERT - depends on PROC_FS - default y - help - Say 'N' to disable Sound proc FS, which may reduce code size about - 9KB on x86_64 platform. - If unsure say Y. + bool "Sound Proc FS Support" if EXPERT + depends on PROC_FS + default y + help + Say 'N' to disable Sound proc FS, which may reduce code size about + 9KB on x86_64 platform. + If unsure say Y. config SND_VERBOSE_PROCFS bool "Verbose procfs contents"
@@ -141,8 +141,8 @@ config SND_VERBOSE_PROCFS default y help Say Y here to include code for verbose procfs contents (provides - useful information to developers when a problem occurs). On the - other side, it makes the ALSA subsystem larger. + useful information to developers when a problem occurs). On the + other side, it makes the ALSA subsystem larger. config SND_VERBOSE_PRINTK bool "Verbose printk"
@@ -163,7 +163,7 @@ config SND_DEBUG_VERBOSE depends on SND_DEBUG help Say Y here to enable extra-verbose debugging messages. - + Let me repeat: it enables EXTRA-VERBOSE DEBUGGING messages. So, say Y only if you are ready to be annoyed.
sound/firewire/Kconfig +61 -61
154 lines not on this page · raw message
sound/hda/Kconfig +2 -2
@@ -13,8 +13,8 @@ config SND_HDA_I915 select SND_HDA_COMPONENT config SND_HDA_EXT_CORE - tristate - select SND_HDA_CORE + tristate + select SND_HDA_CORE config SND_HDA_PREALLOC_SIZE int "Pre-allocated buffer size for HD-audio driver"
sound/isa/Kconfig +13 -14
@@ -1,22 +1,22 @@ # ALSA ISA drivers config SND_WSS_LIB - tristate - select SND_PCM + tristate + select SND_PCM select SND_TIMER config SND_SB_COMMON - tristate + tristate config SND_SB8_DSP - tristate - select SND_PCM - select SND_SB_COMMON + tristate + select SND_PCM + select SND_SB_COMMON config SND_SB16_DSP - tristate - select SND_PCM - select SND_SB_COMMON + tristate + select SND_PCM + select SND_SB_COMMON menuconfig SND_ISA bool "ISA sound devices"
@@ -58,7 +58,7 @@ config SND_AD1848 help Say Y here to include support for AD1848 (Analog Devices) or CS4248 (Cirrus Logic - Crystal Semiconductors) chips. - + For newer chips from Cirrus Logic, use the CS4231 or CS4232+ drivers.
@@ -343,7 +343,7 @@ config SND_MIRO select SND_MPU401_UART select SND_PCM help - Say 'Y' or 'M' to include support for Miro miroSOUND PCM1 pro, + Say 'Y' or 'M' to include support for Miro miroSOUND PCM1 pro, miroSOUND PCM12 and miroSOUND PCM20 Radio soundcards. To compile this driver as a module, choose M here: the module
@@ -408,7 +408,7 @@ config SND_SSCAPE select SND_WSS_LIB select FW_LOADER help - Say Y here to include support for Ensoniq SoundScape + Say Y here to include support for Ensoniq SoundScape and Ensoniq OEM soundcards. The PCM audio is supported on SoundScape Classic, Elite, PnP
@@ -467,5 +467,4 @@ config SND_MSND_CLASSIC To compile this driver as a module, choose M here: the module will be called snd-msnd-classic. -endif # SND_ISA - +endif # SND_ISA
sound/mips/Kconfig +7 -8
@@ -13,15 +13,14 @@ config SND_SGI_O2 tristate "SGI O2 Audio" depends on SGI_IP32 select SND_PCM - help - Sound support for the SGI O2 Workstation. + help + Sound support for the SGI O2 Workstation. config SND_SGI_HAL2 - tristate "SGI HAL2 Audio" - depends on SGI_HAS_HAL2 + tristate "SGI HAL2 Audio" + depends on SGI_HAS_HAL2 select SND_PCM - help - Sound support for the SGI Indy and Indigo2 Workstation. - -endif # SND_MIPS + help + Sound support for the SGI Indy and Indigo2 Workstation. +endif # SND_MIPS
sound/parisc/Kconfig +1 -1
@@ -17,4 +17,4 @@ config SND_HARMONY chip found in most GSC-based PA-RISC workstations. It's frequently provided as part of the Lasi multi-function IC. -endif # SND_GSC +endif # SND_GSC
sound/pci/Kconfig +2 -2
@@ -216,7 +216,7 @@ config SND_CMIPCI will be called snd-cmipci. config SND_OXYGEN_LIB - tristate + tristate config SND_OXYGEN tristate "C-Media 8786, 8787, 8788 (Oxygen)"
@@ -907,6 +907,6 @@ config SND_YMFPCI To compile this driver as a module, choose M here: the module will be called snd-ymfpci. -endif # SND_PCI +endif # SND_PCI source "sound/pci/hda/Kconfig"
sound/pcmcia/Kconfig +1 -2
@@ -29,5 +29,4 @@ config SND_PDAUDIOCF To compile this driver as a module, choose M here: the module will be called snd-pdaudiocf. -endif # SND_PCMCIA - +endif # SND_PCMCIA
sound/ppc/Kconfig +1 -1
@@ -49,4 +49,4 @@ config SND_PS3_DEFAULT_START_DELAY depends on SND_PS3 default "2000" -endif # SND_PPC +endif # SND_PPC
sound/sh/Kconfig +1 -2
@@ -27,5 +27,4 @@ config SND_SH_DAC_AUDIO help Say Y here to include support for the on-chip DAC. -endif # SND_SUPERH - +endif # SND_SUPERH
sound/soc/Kconfig +2 -3
@@ -13,7 +13,7 @@ menuconfig SND_SOC If you want ASoC support, you should say Y here and also to the specific driver for your SoC platform below. - + ASoC provides power efficient ALSA support for embedded battery powered SoC based systems like PDA's, Phones and Personal Media Players.
@@ -83,5 +83,4 @@ source "sound/soc/codecs/Kconfig" # generic frame-work source "sound/soc/generic/Kconfig" -endif # SND_SOC - +endif # SND_SOC
sound/soc/amd/Kconfig +4 -4
@@ -1,7 +1,7 @@ config SND_SOC_AMD_ACP tristate "AMD Audio Coprocessor support" help - This option enables ACP DMA support on AMD platform. + This option enables ACP DMA support on AMD platform. config SND_SOC_AMD_CZ_DA7219MX98357_MACH tristate "AMD CZ support for DA7219 and MAX9835"
@@ -11,17 +11,17 @@ config SND_SOC_AMD_CZ_DA7219MX98357_MACH select REGULATOR depends on SND_SOC_AMD_ACP && I2C help - This option enables machine driver for DA7219 and MAX9835. + This option enables machine driver for DA7219 and MAX9835. config SND_SOC_AMD_CZ_RT5645_MACH tristate "AMD CZ support for RT5645" select SND_SOC_RT5645 depends on SND_SOC_AMD_ACP && I2C help - This option enables machine driver for rt5645. + This option enables machine driver for rt5645. config SND_SOC_AMD_ACP3x tristate "AMD Audio Coprocessor-v3.x support" depends on X86 && PCI help - This option enables ACP v3.x I2S support on AMD platform + This option enables ACP v3.x I2S support on AMD platform
sound/soc/cirrus/Kconfig +7 -7
@@ -32,13 +32,13 @@ config SND_EP93XX_SOC_AC97 select SND_SOC_AC97_BUS config SND_EP93XX_SOC_SNAPPERCL15 - tristate "SoC Audio support for Bluewater Systems Snapper CL15 module" - depends on SND_EP93XX_SOC && MACH_SNAPPER_CL15 && I2C - select SND_EP93XX_SOC_I2S - select SND_SOC_TLV320AIC23_I2C - help - Say Y or M here if you want to add support for I2S audio on the - Bluewater Systems Snapper CL15 module. + tristate "SoC Audio support for Bluewater Systems Snapper CL15 module" + depends on SND_EP93XX_SOC && MACH_SNAPPER_CL15 && I2C + select SND_EP93XX_SOC_I2S + select SND_SOC_TLV320AIC23_I2C + help + Say Y or M here if you want to add support for I2S audio on the + Bluewater Systems Snapper CL15 module. config SND_EP93XX_SOC_SIMONE tristate "SoC Audio support for Simplemachines Sim.One board"
sound/soc/codecs/Kconfig +30 -30
165 lines not on this page · raw message
sound/soc/dwc/Kconfig +7 -8
@@ -3,17 +3,16 @@ config SND_DESIGNWARE_I2S depends on CLKDEV_LOOKUP select SND_SOC_GENERIC_DMAENGINE_PCM help - Say Y or M if you want to add support for I2S driver for - Synopsys designware I2S device. The device supports up to - a maximum of 8 channels each for play and record. + Say Y or M if you want to add support for I2S driver for + Synopsys designware I2S device. The device supports up to + a maximum of 8 channels each for play and record. config SND_DESIGNWARE_PCM bool "PCM PIO extension for I2S driver" depends on SND_DESIGNWARE_I2S help - Say Y or N if you want to add a custom ALSA extension that registers - a PCM and uses PIO to transfer data. - - This functionality is specially suited for I2S devices that don't have - DMA support. + Say Y or N if you want to add a custom ALSA extension that registers + a PCM and uses PIO to transfer data. + This functionality is specially suited for I2S devices that don't have + DMA support.
sound/soc/fsl/Kconfig +4 -4
@@ -291,10 +291,10 @@ config SND_SOC_FSL_ASOC_CARD select SND_SOC_FSL_SAI select SND_SOC_FSL_SSI help - ALSA SoC Audio support with ASRC feature for Freescale SoCs that have - ESAI/SAI/SSI and connect with external CODECs such as WM8962, CS42888, - CS4271, CS4272 and SGTL5000. - Say Y if you want to add support for Freescale Generic ASoC Sound Card. + ALSA SoC Audio support with ASRC feature for Freescale SoCs that have + ESAI/SAI/SSI and connect with external CODECs such as WM8962, CS42888, + CS4271, CS4272 and SGTL5000. + Say Y if you want to add support for Freescale Generic ASoC Sound Card. endif # SND_IMX_SOC
sound/soc/generic/Kconfig +1 -1
@@ -1,5 +1,5 @@ config SND_SIMPLE_CARD_UTILS - tristate + tristate config SND_SIMPLE_CARD tristate "ASoC Simple sound card support"
sound/soc/intel/Kconfig +1 -1
@@ -111,7 +111,7 @@ config SND_SOC_INTEL_SKYLAKE select SND_SOC_INTEL_CNL select SND_SOC_INTEL_CFL help - This is a backwards-compatible option to select all devices + This is a backwards-compatible option to select all devices supported by the Intel SST/Skylake driver. This option is no longer recommended and will be deprecated when the SOF driver is introduced. Distributions should explicitly
sound/soc/intel/boards/Kconfig +41 -41
131 lines not on this page · raw message
sound/soc/jz4740/Kconfig +1 -1
@@ -21,7 +21,7 @@ config SND_JZ4740_SOC_QI_LB60 depends on HAS_IOMEM depends on JZ4740_QI_LB60 || COMPILE_TEST select SND_JZ4740_SOC_I2S - select SND_SOC_JZ4740_CODEC + select SND_SOC_JZ4740_CODEC help Say Y if you want to add support for ASoC audio on the Qi LB60 board a.k.a Qi Ben NanoNote.
sound/soc/mxs/Kconfig +1 -2
@@ -7,7 +7,6 @@ menuconfig SND_MXS_SOC Say Y or M if you want to add support for codecs attached to the MXS SAIF interface. - if SND_MXS_SOC config SND_SOC_MXS_SGTL5000
@@ -18,4 +17,4 @@ config SND_SOC_MXS_SGTL5000 Say Y if you want to add support for SoC audio on an MXS board with a sgtl5000 codec. -endif # SND_MXS_SOC +endif # SND_MXS_SOC
sound/soc/pxa/Kconfig +14 -15
@@ -157,7 +157,6 @@ config SND_SOC_TTC_DKB help Say Y if you want to add support for SoC audio on TTC DKB - config SND_SOC_ZYLONITE tristate "SoC Audio support for Marvell Zylonite" depends on SND_PXA2XX_SOC && MACH_ZYLONITE
@@ -189,23 +188,23 @@ config SND_PXA2XX_SOC_MAGICIAN HTC Magician. config SND_PXA2XX_SOC_MIOA701 - tristate "SoC Audio support for MIO A701" - depends on SND_PXA2XX_SOC && MACH_MIOA701 + tristate "SoC Audio support for MIO A701" + depends on SND_PXA2XX_SOC && MACH_MIOA701 depends on AC97_BUS=n - select SND_PXA2XX_SOC_AC97 - select SND_SOC_WM9713 - help - Say Y if you want to add support for SoC audio on the - MIO A701. + select SND_PXA2XX_SOC_AC97 + select SND_SOC_WM9713 + help + Say Y if you want to add support for SoC audio on the + MIO A701. config SND_PXA2XX_SOC_IMOTE2 - tristate "SoC Audio support for IMote 2" - depends on SND_PXA2XX_SOC && MACH_INTELMOTE2 && I2C - select SND_PXA2XX_SOC_I2S - select SND_SOC_WM8940 - help - Say Y if you want to add support for SoC audio on the - IMote 2. + tristate "SoC Audio support for IMote 2" + depends on SND_PXA2XX_SOC && MACH_INTELMOTE2 && I2C + select SND_PXA2XX_SOC_I2S + select SND_SOC_WM8940 + help + Say Y if you want to add support for SoC audio on the + IMote 2. config SND_MMP_SOC_BROWNSTONE tristate "SoC Audio support for Marvell Brownstone"
sound/soc/samsung/Kconfig +4 -4
@@ -194,10 +194,10 @@ config SND_SOC_ODROID Say Y here to enable audio support for the Odroid XU3/XU4. config SND_SOC_ARNDALE_RT5631_ALC5631 - tristate "Audio support for RT5631(ALC5631) on Arndale Board" - depends on I2C - select SND_SAMSUNG_I2S - select SND_SOC_RT5631 + tristate "Audio support for RT5631(ALC5631) on Arndale Board" + depends on I2C + select SND_SAMSUNG_I2S + select SND_SOC_RT5631 config SND_SOC_SAMSUNG_TM2_WM5110 tristate "SoC I2S Audio support for WM5110 on TM2 board"
sound/soc/zte/Kconfig +6 -6
@@ -17,9 +17,9 @@ config ZX_I2S ZTE ZX I2S interface config ZX_TDM - tristate "ZTE ZX TDM Driver Support" - depends on COMMON_CLK - select SND_SOC_GENERIC_DMAENGINE_PCM - help - Say Y or M if you want to add support for codecs attached to the - ZTE ZX TDM interface + tristate "ZTE ZX TDM Driver Support" + depends on COMMON_CLK + select SND_SOC_GENERIC_DMAENGINE_PCM + help + Say Y or M if you want to add support for codecs attached to the + ZTE ZX TDM interface
sound/sparc/Kconfig +1 -1
@@ -39,4 +39,4 @@ config SND_SUN_DBRI To compile this driver as a module, choose M here: the module will be called snd-sun-dbri. -endif # SND_SPARC +endif # SND_SPARC
sound/spi/Kconfig +1 -2
@@ -34,5 +34,4 @@ config SND_AT73C213_TARGET_BITRATE Set to 48000 Hz by default. -endif # SND_SPI - +endif # SND_SPI
sound/usb/Kconfig +23 -24
76 lines not on this page · raw message
sound/x86/Kconfig +2 -2
@@ -12,6 +12,6 @@ config HDMI_LPE_AUDIO depends on DRM_I915 select SND_PCM help - Choose this option to support HDMI LPE Audio mode + Choose this option to support HDMI LPE Audio mode -endif # SND_X86 +endif # SND_X86
Signature · 1 line
1.9.1
PATCH 33/114 mm: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- mm/Kconfig | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 deletions(-)
mm/Kconfig +20 -20
@@ -123,9 +123,9 @@ config SPARSEMEM_VMEMMAP depends on SPARSEMEM && SPARSEMEM_VMEMMAP_ENABLE default y help - SPARSEMEM_VMEMMAP uses a virtually mapped memmap to optimise - pfn_to_page and page_to_pfn operations. This is the most - efficient option when sufficient kernel resources are available. + SPARSEMEM_VMEMMAP uses a virtually mapped memmap to optimise + pfn_to_page and page_to_pfn operations. This is the most + efficient option when sufficient kernel resources are available. config HAVE_MEMBLOCK_NODE_MAP bool
@@ -160,10 +160,10 @@ config MEMORY_HOTPLUG_SPARSE depends on SPARSEMEM && MEMORY_HOTPLUG config MEMORY_HOTPLUG_DEFAULT_ONLINE - bool "Online the newly added memory blocks by default" - default n - depends on MEMORY_HOTPLUG - help + bool "Online the newly added memory blocks by default" + default n + depends on MEMORY_HOTPLUG + help This option sets the default policy setting for memory hotplug onlining policy (/sys/devices/system/memory/auto_online_blocks) which determines what happens to newly added memory regions. Policy setting
@@ -228,14 +228,14 @@ config COMPACTION select MIGRATION depends on MMU help - Compaction is the only memory management component to form - high order (larger physically contiguous) memory blocks - reliably. The page allocator relies on compaction heavily and - the lack of the feature can lead to unexpected OOM killer - invocations for high order memory requests. You shouldn't - disable this option unless there really is a strong reason for - it and then we would be really interested to hear about that at - [email protected]. + Compaction is the only memory management component to form + high order (larger physically contiguous) memory blocks + reliably. The page allocator relies on compaction heavily and + the lack of the feature can lead to unexpected OOM killer + invocations for high order memory requests. You shouldn't + disable this option unless there really is a strong reason for + it and then we would be really interested to hear about that at + [email protected]. # # support for page migration
@@ -304,10 +304,10 @@ config KSM root has set /sys/kernel/mm/ksm/run to 1 (if CONFIG_SYSFS is set). config DEFAULT_MMAP_MIN_ADDR - int "Low address space to protect from user allocation" + int "Low address space to protect from user allocation" depends on MMU - default 4096 - help + default 4096 + help This is the portion of low virtual memory which should be protected from userspace allocation. Keeping a user from writing to low pages can help reduce the impact of kernel NULL pointer bugs.
@@ -400,7 +400,7 @@ choice benefit but it will work automatically for all applications. config TRANSPARENT_HUGEPAGE_MADVISE - bool "madvise" + bool "madvise" help Enabling Transparent Hugepage madvise, will only provide a performance improvement benefit to the applications using
@@ -410,7 +410,7 @@ choice endchoice config ARCH_WANTS_THP_SWAP - def_bool n + def_bool n config THP_SWAP def_bool y
Signature · 1 line
1.9.1
PATCH 34/114 arch: arm: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/arm/Kconfig | 24 +++++++++++----------- arch/arm/mach-aspeed/Kconfig | 10 ++++----- arch/arm/mach-ep93xx/Kconfig | 8 ++++---- arch/arm/mach-hisi/Kconfig | 14 ++++++------- arch/arm/mach-ixp4xx/Kconfig | 32 ++++++++++++++--------------- arch/arm/mach-mmp/Kconfig | 2 +- arch/arm/mach-omap1/Kconfig | 36 ++++++++++++++++---------------- arch/arm/mach-omap2/Kconfig | 12 +++++------ arch/arm/mach-prima2/Kconfig | 6 +++--- arch/arm/mach-s3c24xx/Kconfig | 32 ++++++++++++++--------------- arch/arm/mach-s3c64xx/Kconfig | 16 +++++++-------- arch/arm/mach-sa1100/Kconfig | 4 ++-- arch/arm/mach-vt8500/Kconfig | 6 +++--- arch/arm/mach-w90x900/Kconfig | 6 +++--- arch/arm/mm/Kconfig | 48 +++++++++++++++++++++---------------------- arch/arm/plat-samsung/Kconfig | 26 +++++++++++------------ 16 files changed, 140 insertions(+), 142 deletions(-)
arch/arm/Kconfig +12 -12
@@ -1115,14 +1115,14 @@ config ARM_ERRATA_764369 in the diagnostic control register of the SCU. config ARM_ERRATA_775420 - bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock" - depends on CPU_V7 - help - This option enables the workaround for the 775420 Cortex-A9 (r2p2, - r2p6,r2p8,r2p10,r3p0) erratum. In case a date cache maintenance - operation aborts with MMU exception, it might cause the processor - to deadlock. This workaround puts DSB before executing ISB if - an abort may occur on cache maintenance. + bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock" + depends on CPU_V7 + help + This option enables the workaround for the 775420 Cortex-A9 (r2p2, + r2p6,r2p8,r2p10,r3p0) erratum. In case a date cache maintenance + operation aborts with MMU exception, it might cause the processor + to deadlock. This workaround puts DSB before executing ISB if + an abort may occur on cache maintenance. config ARM_ERRATA_798181 bool "ARM errata: TLBI/DSB failure on Cortex-A15"
@@ -1650,12 +1650,12 @@ config HW_PERF_EVENTS depends on ARM_PMU config SYS_SUPPORTS_HUGETLBFS - def_bool y - depends on ARM_LPAE + def_bool y + depends on ARM_LPAE config HAVE_ARCH_TRANSPARENT_HUGEPAGE - def_bool y - depends on ARM_LPAE + def_bool y + depends on ARM_LPAE config ARCH_WANT_GENERAL_HUGETLB def_bool y
arch/arm/mach-aspeed/Kconfig +5 -5
@@ -18,9 +18,9 @@ config MACH_ASPEED_G4 select CPU_ARM926T select PINCTRL_ASPEED_G4 help - Say yes if you intend to run on an Aspeed ast2400 or similar - fourth generation BMCs, such as those used by OpenPower Power8 - systems. + Say yes if you intend to run on an Aspeed ast2400 or similar + fourth generation BMCs, such as those used by OpenPower Power8 + systems. config MACH_ASPEED_G5 bool "Aspeed SoC 5th Generation"
@@ -28,7 +28,7 @@ config MACH_ASPEED_G5 select CPU_V6 select PINCTRL_ASPEED_G5 help - Say yes if you intend to run on an Aspeed ast2500 or similar - fifth generation Aspeed BMCs. + Say yes if you intend to run on an Aspeed ast2500 or similar + fifth generation Aspeed BMCs. endif
arch/arm/mach-ep93xx/Kconfig +4 -4
@@ -125,10 +125,10 @@ config MACH_MICRO9S Contec Micro9-Slim board. config MACH_SIM_ONE - bool "Support Simplemachines Sim.One board" - help - Say 'Y' here if you want your kernel to support the - Simplemachines Sim.One board. + bool "Support Simplemachines Sim.One board" + help + Say 'Y' here if you want your kernel to support the + Simplemachines Sim.One board. config MACH_SNAPPER_CL15 bool "Support Bluewater Systems Snapper CL15 Module"
arch/arm/mach-hisi/Kconfig +7 -7
@@ -24,13 +24,13 @@ config ARCH_HI3xxx Support for Hisilicon Hi36xx SoC family config ARCH_HIP01 - bool "Hisilicon HIP01 family" - depends on ARCH_MULTI_V7 - select HAVE_ARM_SCU if SMP - select HAVE_ARM_TWD if SMP - select ARM_GLOBAL_TIMER - help - Support for Hisilicon HIP01 SoC family + bool "Hisilicon HIP01 family" + depends on ARCH_MULTI_V7 + select HAVE_ARM_SCU if SMP + select HAVE_ARM_TWD if SMP + select ARM_GLOBAL_TIMER + help + Support for Hisilicon HIP01 SoC family config ARCH_HIP04 bool "Hisilicon HiP04 Cortex A15 family"
arch/arm/mach-ixp4xx/Kconfig +16 -16
@@ -22,9 +22,9 @@ config MACH_AVILA see <file:Documentation/arm/IXP4xx>. config MACH_LOFT - bool "Loft" - depends on MACH_AVILA - help + bool "Loft" + depends on MACH_AVILA + help Say 'Y' here if you want your kernel to support the Giant Shoulder Inc Loft board (a minor variation on the standard Gateworks Avila Network Platform).
@@ -33,7 +33,7 @@ config ARCH_ADI_COYOTE bool "Coyote" select FORCE_PCI help - Say 'Y' here if you want your kernel to support the ADI + Say 'Y' here if you want your kernel to support the ADI Engineering Coyote Gateway Reference Platform. For more information on this platform, see <file:Documentation/arm/IXP4xx>.
@@ -56,8 +56,8 @@ config MACH_WG302V2 config ARCH_IXDP425 bool "IXDP425" help - Say 'Y' here if you want your kernel to support Intel's - IXDP425 Development Platform (Also known as Richfield). + Say 'Y' here if you want your kernel to support Intel's + IXDP425 Development Platform (Also known as Richfield). For more information on this platform, see <file:Documentation/arm/IXP4xx>. config MACH_IXDPG425
@@ -88,12 +88,12 @@ config MACH_KIXRP435 For more information on this platform, see <file:Documentation/arm/IXP4xx>. # -# IXCDP1100 is the exact same HW as IXDP425, but with a different machine -# number from the bootloader due to marketing monkeys, so we just enable it +# IXCDP1100 is the exact same HW as IXDP425, but with a different machine +# number from the bootloader due to marketing monkeys, so we just enable it # by default if IXDP425 is enabled. # config ARCH_IXCDP1100 - bool + bool depends on ARCH_IXDP425 default y
@@ -200,14 +200,14 @@ config IXP4XX_INDIRECT_PCI bool "Use indirect PCI memory access" depends on PCI help - IXP4xx provides two methods of accessing PCI memory space: + IXP4xx provides two methods of accessing PCI memory space: - 1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB). - To access PCI via this space, we simply ioremap() the BAR - into the kernel and we can use the standard read[bwl]/write[bwl] - macros. This is the preferred method due to speed but it - limits the system to just 64MB of PCI memory. This can be - problematic if using video cards and other memory-heavy devices. + 1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB). + To access PCI via this space, we simply ioremap() the BAR + into the kernel and we can use the standard read[bwl]/write[bwl] + macros. This is the preferred method due to speed but it + limits the system to just 64MB of PCI memory. This can be + problematic if using video cards and other memory-heavy devices. 2) If > 64MB of memory space is required, the IXP4xx can be configured to use indirect registers to access the whole PCI
arch/arm/mach-mmp/Kconfig +1 -1
@@ -149,7 +149,7 @@ config CPU_MMP2 Select code specific to MMP2. MMP2 is ARMv7 compatible. config USB_EHCI_MV_U2O - bool "EHCI support for PXA USB OTG controller" + bool "EHCI support for PXA USB OTG controller" depends on USB_EHCI_MV help Enables support for OTG controller which can be switched to host mode.
arch/arm/mach-omap1/Kconfig +18 -18
@@ -55,7 +55,7 @@ config OMAP_MUX_WARNINGS default y help Choose Y here to warn whenever driver initialization logic needs - to change the pin multiplexing setup. When there are no warnings + to change the pin multiplexing setup. When there are no warnings printed, it's safe to deselect OMAP_MUX for your product. comment "OMAP Board Type"
@@ -65,20 +65,20 @@ config MACH_OMAP_INNOVATOR bool "TI Innovator" depends on ARCH_OMAP1 && (ARCH_OMAP15XX || ARCH_OMAP16XX) help - TI OMAP 1510 or 1610 Innovator board support. Say Y here if you - have such a board. + TI OMAP 1510 or 1610 Innovator board support. Say Y here if you + have such a board. config MACH_OMAP_H2 bool "TI H2 Support" depends on ARCH_OMAP1 && ARCH_OMAP16XX - help + help TI OMAP 1610/1611B H2 board support. Say Y here if you have such a board. config MACH_OMAP_H3 bool "TI H3 Support" depends on ARCH_OMAP1 && ARCH_OMAP16XX - help + help TI OMAP 1710 H3 board support. Say Y here if you have such a board.
@@ -91,14 +91,14 @@ config MACH_HERALD config MACH_OMAP_OSK bool "TI OSK Support" depends on ARCH_OMAP1 && ARCH_OMAP16XX - help + help TI OMAP 5912 OSK (OMAP Starter Kit) board support. Say Y here - if you have such a board. + if you have such a board. config OMAP_OSK_MISTRAL bool "Mistral QVGA board Support" depends on MACH_OMAP_OSK - help + help The OSK supports an optional add-on board with a Quarter-VGA touchscreen, PDA-ish buttons, a resume button, bicolor LED, and camera connector. Say Y here if you have this board.
@@ -106,14 +106,14 @@ config OMAP_OSK_MISTRAL config MACH_OMAP_PERSEUS2 bool "TI Perseus2" depends on ARCH_OMAP1 && ARCH_OMAP730 - help + help Support for TI OMAP 730 Perseus2 board. Say Y here if you have such a board. config MACH_OMAP_FSAMPLE bool "TI F-Sample" depends on ARCH_OMAP1 && ARCH_OMAP730 - help + help Support for TI OMAP 850 F-Sample board. Say Y here if you have such a board.
@@ -130,10 +130,10 @@ config MACH_OMAP_PALMZ71 bool "Palm Zire71" depends on ARCH_OMAP1 && ARCH_OMAP15XX help - Support for the Palm Zire71 PDA. To boot the kernel, - you'll need a PalmOS compatible bootloader; check out - http://hackndev.com/palm/z71 for more information. - Say Y here if you have such a PDA, say N otherwise. + Support for the Palm Zire71 PDA. To boot the kernel, + you'll need a PalmOS compatible bootloader; check out + http://hackndev.com/palm/z71 for more information. + Say Y here if you have such a PDA, say N otherwise. config MACH_OMAP_PALMTT bool "Palm Tungsten|T"
@@ -179,10 +179,10 @@ config MACH_OMAP_GENERIC bool "Generic OMAP board" depends on ARCH_OMAP1 && (ARCH_OMAP15XX || ARCH_OMAP16XX) help - Support for generic OMAP-1510, 1610 or 1710 board with - no FPGA. Can be used as template for porting Linux to - custom OMAP boards. Say Y here if you have a custom - board. + Support for generic OMAP-1510, 1610 or 1710 board with + no FPGA. Can be used as template for porting Linux to + custom OMAP boards. Say Y here if you have a custom + board. endmenu
arch/arm/mach-omap2/Kconfig +6 -6
@@ -174,16 +174,16 @@ config SOC_TI81XX default y config OMAP_PACKAGE_CBC - bool + bool config OMAP_PACKAGE_CBB - bool + bool config OMAP_PACKAGE_CUS - bool + bool config OMAP_PACKAGE_CBP - bool + bool comment "OMAP Legacy Platform Data Board Type" depends on ARCH_OMAP2PLUS
@@ -208,10 +208,10 @@ config MACH_OMAP3_PANDORA select OMAP_PACKAGE_CBB config MACH_NOKIA_N810 - bool + bool config MACH_NOKIA_N810_WIMAX - bool + bool config MACH_NOKIA_N8X0 bool "Nokia N800/N810"
arch/arm/mach-prima2/Kconfig +3 -3
@@ -21,7 +21,7 @@ config ARCH_ATLAS6 default y select SIRF_IRQ help - Support for CSR SiRFSoC ARM Cortex A9 Platform + Support for CSR SiRFSoC ARM Cortex A9 Platform config ARCH_ATLAS7 bool "CSR SiRFSoC ATLAS7 ARM Cortex A7 Platform"
@@ -31,7 +31,7 @@ config ARCH_ATLAS7 select HAVE_ARM_SCU if SMP select HAVE_SMP help - Support for CSR SiRFSoC ARM Cortex A7 Platform + Support for CSR SiRFSoC ARM Cortex A7 Platform config ARCH_PRIMA2 bool "CSR SiRFSoC PRIMA2 ARM Cortex A9 Platform"
@@ -40,7 +40,7 @@ config ARCH_PRIMA2 select ZONE_DMA select PRIMA2_TIMER help - Support for CSR SiRFSoC ARM Cortex A9 Platform + Support for CSR SiRFSoC ARM Cortex A9 Platform config SIRF_IRQ bool
arch/arm/mach-s3c24xx/Kconfig +15 -17
@@ -17,8 +17,6 @@ config PLAT_S3C24XX help Base platform code for any Samsung S3C24XX device - - menu "SAMSUNG S3C24XX SoCs Support" comment "S3C24XX SoCs"
@@ -138,11 +136,11 @@ config S3C2410_IOTIMING and s3c2440/s3c2442 cpu frequency support. config S3C2410_CPUFREQ_UTILS - bool - depends on ARM_S3C24XX_CPUFREQ - help - Internal node to select timing code that is common to the s3c2410 - and s3c2440/s3c244 cpu frequency support. + bool + depends on ARM_S3C24XX_CPUFREQ + help + Internal node to select timing code that is common to the s3c2410 + and s3c2440/s3c244 cpu frequency support. # cpu frequency support common to s3c2412, s3c2413 and s3c2442
@@ -280,7 +278,7 @@ config MACH_VR1000 help Say Y here if you are using the Thorcom VR1000 board. -endif # CPU_S3C2410 +endif # CPU_S3C2410 config S3C2412_PM_SLEEP bool
@@ -354,7 +352,7 @@ config MACH_VSTMS help Say Y here if you are using an VSTMS board -endif # CPU_S3C2412 +endif # CPU_S3C2412 if CPU_S3C2416
@@ -402,7 +400,7 @@ config MACH_S3C2416_DT Note: This is under development and not all peripherals can be supported with this machine file. -endif # CPU_S3C2416 +endif # CPU_S3C2416 if CPU_S3C2440 || CPU_S3C2442
@@ -528,7 +526,7 @@ config SMDK2440_CPU2440 default y if ARCH_S3C2440 select S3C2440_XTAL_16934400 -endif # CPU_S3C2440 +endif # CPU_S3C2440 if CPU_S3C2442
@@ -548,7 +546,7 @@ config MACH_NEO1973_GTA02 select S3C24XX_PWM select S3C_DEV_USB_HOST help - Say Y here if you are using the Openmoko GTA02 / Freerunner GSM Phone + Say Y here if you are using the Openmoko GTA02 / Freerunner GSM Phone config MACH_RX1950 bool "HP iPAQ rx1950"
@@ -560,9 +558,9 @@ config MACH_RX1950 select S3C24XX_PWM select S3C_DEV_NAND help - Say Y here if you're using HP iPAQ rx1950 + Say Y here if you're using HP iPAQ rx1950 -endif # CPU_S3C2442 +endif # CPU_S3C2442 if CPU_S3C2443 || CPU_S3C2416
@@ -571,7 +569,7 @@ config S3C2443_SETUP_SPI help Common setup code for SPI GPIO configurations -endif # CPU_S3C2443 || CPU_S3C2416 +endif # CPU_S3C2443 || CPU_S3C2416 if CPU_S3C2443
@@ -584,7 +582,7 @@ config MACH_SMDK2443 help Say Y here if you are using an SMDK2443 -endif # CPU_S3C2443 +endif # CPU_S3C2443 config PM_H1940 bool
@@ -593,4 +591,4 @@ config PM_H1940 endmenu # SAMSUNG S3C24XX SoCs Support -endif # ARCH_S3C24XX +endif # ARCH_S3C24XX
arch/arm/mach-s3c64xx/Kconfig +8 -8
@@ -100,7 +100,7 @@ config S3C64XX_SETUP_SDHCI_GPIO config S3C64XX_SETUP_SPI bool help - Common setup code for SPI GPIO configurations + Common setup code for SPI GPIO configurations config S3C64XX_SETUP_USB_PHY bool
@@ -110,7 +110,7 @@ config S3C64XX_SETUP_USB_PHY # S36400 Macchine support config MACH_SMDK6400 - bool "SMDK6400" + bool "SMDK6400" depends on ATAGS select CPU_S3C6400 select S3C64XX_SETUP_SDHCI
@@ -202,7 +202,7 @@ config SMDK6410_SD_CH0 bool "Use channel 0 only" depends on MACH_SMDK6410 help - Select CON7 (channel 0) as the MMC/SD slot, as + Select CON7 (channel 0) as the MMC/SD slot, as at least some SMDK6410 boards come with the resistors fitted so that the card detects for channels 0 and 1 are the same.
@@ -211,7 +211,7 @@ config SMDK6410_SD_CH1 bool "Use channel 1 only" depends on MACH_SMDK6410 help - Select CON6 (channel 1) as the MMC/SD slot, as + Select CON6 (channel 1) as the MMC/SD slot, as at least some SMDK6410 boards come with the resistors fitted so that the card detects for channels 0 and 1 are the same.
@@ -257,7 +257,7 @@ config MACH_NCP select S3C_DEV_HSMMC1 select S3C_DEV_I2C1 help - Machine support for the Samsung NCP + Machine support for the Samsung NCP config MACH_HMT bool "Airgoo HMT"
@@ -289,21 +289,21 @@ config MACH_SMARTQ select SAMSUNG_DEV_PWM select SAMSUNG_DEV_TS help - Shared machine support for SmartQ 5/7 + Shared machine support for SmartQ 5/7 config MACH_SMARTQ5 bool "SmartQ 5" depends on ATAGS select MACH_SMARTQ help - Machine support for the SmartQ 5 + Machine support for the SmartQ 5 config MACH_SMARTQ7 bool "SmartQ 7" depends on ATAGS select MACH_SMARTQ help - Machine support for the SmartQ 7 + Machine support for the SmartQ 7 config MACH_WLF_CRAGG_6410 bool "Wolfson Cragganmore 6410"
arch/arm/mach-sa1100/Kconfig +2 -2
@@ -91,8 +91,8 @@ config SA1100_JORNADA720 select SA1111 help Say Y here if you want to build a kernel for the HP Jornada 720 - handheld computer. See - <http://h10025.www1.hp.com/ewfrf/wc/product?product=61677&cc=us&lc=en&dlc=en&product=61677#> + handheld computer. See + <http://h10025.www1.hp.com/ewfrf/wc/product?product=61677&cc=us&lc=en&dlc=en&product=61677#> config SA1100_JORNADA720_SSP bool "HP Jornada 720 Extended SSP driver"
arch/arm/mach-vt8500/Kconfig +3 -3
@@ -10,9 +10,9 @@ config ARCH_VT8500 config ARCH_WM8505 bool "VIA/Wondermedia 85xx and WM8650" - depends on ARCH_MULTI_V5 - select ARCH_VT8500 - select CPU_ARM926T + depends on ARCH_MULTI_V5 + select ARCH_VT8500 + select CPU_ARM926T config ARCH_WM8750 bool "WonderMedia WM8750"
arch/arm/mach-w90x900/Kconfig +3 -3
@@ -23,7 +23,7 @@ config MACH_W90P910EVB default y select CPU_W90P910 help - Say Y here if you are using the Nuvoton W90P910EVB + Say Y here if you are using the Nuvoton W90P910EVB endmenu
@@ -33,7 +33,7 @@ config MACH_W90P950EVB bool "Nuvoton NUC950 Evaluation Board" select CPU_NUC950 help - Say Y here if you are using the Nuvoton NUC950EVB + Say Y here if you are using the Nuvoton NUC950EVB endmenu
@@ -43,7 +43,7 @@ config MACH_W90N960EVB bool "Nuvoton NUC960 Evaluation Board" select CPU_NUC960 help - Say Y here if you are using the Nuvoton NUC960EVB + Say Y here if you are using the Nuvoton NUC960EVB endmenu
arch/arm/mm/Kconfig +24 -24
70 lines not on this page · raw message
arch/arm/plat-samsung/Kconfig +13 -13
@@ -39,12 +39,12 @@ config SAMSUNG_ATAGS def_bool n depends on ATAGS help - This option enables ATAGS based boot support code for - Samsung platforms, including static platform devices, legacy - clock, timer and interrupt initialization, etc. + This option enables ATAGS based boot support code for + Samsung platforms, including static platform devices, legacy + clock, timer and interrupt initialization, etc. - Platforms that support only DT based boot need not to select - this option. + Platforms that support only DT based boot need not to select + this option. if SAMSUNG_ATAGS
@@ -98,7 +98,7 @@ config S3C_DEV_HSMMC3 config S3C_DEV_HWMON bool help - Compile in platform device definitions for HWMON + Compile in platform device definitions for HWMON config S3C_DEV_I2C1 bool
@@ -202,7 +202,7 @@ config S3C64XX_DEV_SPI2 config SAMSUNG_DEV_TS bool help - Common in platform device definitions for touchscreen device + Common in platform device definitions for touchscreen device config SAMSUNG_DEV_KEYPAD bool
@@ -247,13 +247,13 @@ config SAMSUNG_PM_DEBUG for more information. config S3C_PM_DEBUG_LED_SMDK - bool "SMDK LED suspend/resume debugging" - depends on PM && (MACH_SMDK6410) - help - Say Y here to enable the use of the SMDK LEDs on the baseboard - for debugging of the state of the suspend and resume process. + bool "SMDK LED suspend/resume debugging" + depends on PM && (MACH_SMDK6410) + help + Say Y here to enable the use of the SMDK LEDs on the baseboard + for debugging of the state of the suspend and resume process. - Note, this currently only works for S3C64XX based SMDK boards. + Note, this currently only works for S3C64XX based SMDK boards. config SAMSUNG_PM_CHECK bool "S3C2410 PM Suspend Memory CRC"
Signature · 1 line
1.9.1
Re: [PATCH 034/114] arch: arm: Kconfig: pedantic formatting
Quoted 7 lines · metux IT consult
Formatting of
Kconfigfiles doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.Signed-off-by Enrico Weigelt, metux IT consult <[email protected]>--- arch/arm/Kconfig | 24 +++++++++++-----------
While you are touching this file,
why don't fix checkpatch.pl warning?
WARNING: prefer 'help' over '---help---' for new help texts #1725: FILE: arch/arm/Kconfig:1725:
+config SECCOMP
Quoted 780 lines
arch/arm/mach-aspeed/Kconfig | 10 ++++----- arch/arm/mach-ep93xx/Kconfig | 8 ++++---- arch/arm/mach-hisi/Kconfig | 14 ++++++------- arch/arm/mach-ixp4xx/Kconfig | 32 ++++++++++++++--------------- arch/arm/mach-mmp/Kconfig | 2 +- arch/arm/mach-omap1/Kconfig | 36 ++++++++++++++++---------------- arch/arm/mach-omap2/Kconfig | 12 +++++------ arch/arm/mach-prima2/Kconfig | 6 +++--- arch/arm/mach-s3c24xx/Kconfig | 32 ++++++++++++++--------------- arch/arm/mach-s3c64xx/Kconfig | 16 +++++++-------- arch/arm/mach-sa1100/Kconfig | 4 ++-- arch/arm/mach-vt8500/Kconfig | 6 +++--- arch/arm/mach-w90x900/Kconfig | 6 +++--- arch/arm/mm/Kconfig | 48 +++++++++++++++++++++---------------------- arch/arm/plat-samsung/Kconfig | 26 +++++++++++------------ 16 files changed, 140 insertions(+), 142 deletions(-)arch/arm/Kconfig +12
-12@@ -1115,14 +1115,14 @@ config ARM_ERRATA_764369 in the diagnostic control register of the SCU. config ARM_ERRATA_775420 - bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock" - depends on CPU_V7 - help - This option enables the workaround for the 775420 Cortex-A9 (r2p2, - r2p6,r2p8,r2p10,r3p0) erratum. In case a date cache maintenance - operation aborts with MMU exception, it might cause the processor - to deadlock. This workaround puts DSB before executing ISB if - an abort may occur on cache maintenance. + bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock" + depends on CPU_V7 + help + This option enables the workaround for the 775420 Cortex-A9 (r2p2, + r2p6,r2p8,r2p10,r3p0) erratum. In case a date cache maintenance + operation aborts with MMU exception, it might cause the processor + to deadlock. This workaround puts DSB before executing ISB if + an abort may occur on cache maintenance. config ARM_ERRATA_798181 bool "ARM errata: TLBI/DSB failure on Cortex-A15"@@ -1650,12 +1650,12 @@ config HW_PERF_EVENTS depends on ARM_PMU config SYS_SUPPORTS_HUGETLBFS - def_bool y - depends on ARM_LPAE + def_bool y + depends on ARM_LPAE config HAVE_ARCH_TRANSPARENT_HUGEPAGE - def_bool y - depends on ARM_LPAE + def_bool y + depends on ARM_LPAE config ARCH_WANT_GENERAL_HUGETLB def_bool yarch/arm/mach-aspeed/Kconfig +5
-5@@ -18,9 +18,9 @@ config MACH_ASPEED_G4 select CPU_ARM926T select PINCTRL_ASPEED_G4 help - Say yes if you intend to run on an Aspeed ast2400 or similar - fourth generation BMCs, such as those used by OpenPower Power8 - systems. + Say yes if you intend to run on an Aspeed ast2400 or similar + fourth generation BMCs, such as those used by OpenPower Power8 + systems. config MACH_ASPEED_G5 bool "Aspeed SoC 5th Generation"@@ -28,7 +28,7 @@ config MACH_ASPEED_G5 select CPU_V6 select PINCTRL_ASPEED_G5 help - Say yes if you intend to run on an Aspeed ast2500 or similar - fifth generation Aspeed BMCs. + Say yes if you intend to run on an Aspeed ast2500 or similar + fifth generation Aspeed BMCs. endifarch/arm/mach-ep93xx/Kconfig +4
-4@@ -125,10 +125,10 @@ config MACH_MICRO9S Contec Micro9-Slim board. config MACH_SIM_ONE - bool "Support Simplemachines Sim.One board" - help - Say 'Y' here if you want your kernel to support the - Simplemachines Sim.One board. + bool "Support Simplemachines Sim.One board" + help + Say 'Y' here if you want your kernel to support the + Simplemachines Sim.One board. config MACH_SNAPPER_CL15 bool "Support Bluewater Systems Snapper CL15 Module"arch/arm/mach-hisi/Kconfig +7
-7@@ -24,13 +24,13 @@ config ARCH_HI3xxx Support for Hisilicon Hi36xx SoC family config ARCH_HIP01 - bool "Hisilicon HIP01 family" - depends on ARCH_MULTI_V7 - select HAVE_ARM_SCU if SMP - select HAVE_ARM_TWD if SMP - select ARM_GLOBAL_TIMER - help - Support for Hisilicon HIP01 SoC family + bool "Hisilicon HIP01 family" + depends on ARCH_MULTI_V7 + select HAVE_ARM_SCU if SMP + select HAVE_ARM_TWD if SMP + select ARM_GLOBAL_TIMER + help + Support for Hisilicon HIP01 SoC family config ARCH_HIP04 bool "Hisilicon HiP04 Cortex A15 family"arch/arm/mach-ixp4xx/Kconfig +16
-16@@ -22,9 +22,9 @@ config MACH_AVILA see <file:Documentation/arm/IXP4xx>. config MACH_LOFT - bool "Loft" - depends on MACH_AVILA - help + bool "Loft" + depends on MACH_AVILA + help Say 'Y' here if you want your kernel to support the Giant Shoulder Inc Loft board (a minor variation on the standard Gateworks Avila Network Platform).@@ -33,7 +33,7 @@ config ARCH_ADI_COYOTE bool "Coyote" select FORCE_PCI help - Say 'Y' here if you want your kernel to support the ADI + Say 'Y' here if you want your kernel to support the ADI Engineering Coyote Gateway Reference Platform. For more information on this platform, see <file:Documentation/arm/IXP4xx>.@@ -56,8 +56,8 @@ config MACH_WG302V2 config ARCH_IXDP425 bool "IXDP425" help - Say 'Y' here if you want your kernel to support Intel's - IXDP425 Development Platform (Also known as Richfield). + Say 'Y' here if you want your kernel to support Intel's + IXDP425 Development Platform (Also known as Richfield). For more information on this platform, see <file:Documentation/arm/IXP4xx>. config MACH_IXDPG425@@ -88,12 +88,12 @@ config MACH_KIXRP435 For more information on this platform, see <file:Documentation/arm/IXP4xx>. # -# IXCDP1100 is the exact same HW as IXDP425, but with a different machine -# number from the bootloader due to marketing monkeys, so we just enable it +# IXCDP1100 is the exact same HW as IXDP425, but with a different machine +# number from the bootloader due to marketing monkeys, so we just enable it # by default if IXDP425 is enabled. # config ARCH_IXCDP1100 - bool + bool depends on ARCH_IXDP425 default y@@ -200,14 +200,14 @@ config IXP4XX_INDIRECT_PCI bool "Use indirect PCI memory access" depends on PCI help - IXP4xx provides two methods of accessing PCI memory space: + IXP4xx provides two methods of accessing PCI memory space: - 1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB). - To access PCI via this space, we simply ioremap() the BAR - into the kernel and we can use the standard read[bwl]/write[bwl] - macros. This is the preferred method due to speed but it - limits the system to just 64MB of PCI memory. This can be - problematic if using video cards and other memory-heavy devices. + 1) A direct mapped window from 0x48000000 to 0x4BFFFFFF (64MB). + To access PCI via this space, we simply ioremap() the BAR + into the kernel and we can use the standard read[bwl]/write[bwl] + macros. This is the preferred method due to speed but it + limits the system to just 64MB of PCI memory. This can be + problematic if using video cards and other memory-heavy devices. 2) If > 64MB of memory space is required, the IXP4xx can be configured to use indirect registers to access the whole PCIarch/arm/mach-mmp/Kconfig +1
-1@@ -149,7 +149,7 @@ config CPU_MMP2 Select code specific to MMP2. MMP2 is ARMv7 compatible. config USB_EHCI_MV_U2O - bool "EHCI support for PXA USB OTG controller" + bool "EHCI support for PXA USB OTG controller" depends on USB_EHCI_MV help Enables support for OTG controller which can be switched to host mode.arch/arm/mach-omap1/Kconfig +18
-18@@ -55,7 +55,7 @@ config OMAP_MUX_WARNINGS default y help Choose Y here to warn whenever driver initialization logic needs - to change the pin multiplexing setup. When there are no warnings + to change the pin multiplexing setup. When there are no warnings printed, it's safe to deselect OMAP_MUX for your product. comment "OMAP Board Type"@@ -65,20 +65,20 @@ config MACH_OMAP_INNOVATOR bool "TI Innovator" depends on ARCH_OMAP1 && (ARCH_OMAP15XX || ARCH_OMAP16XX) help - TI OMAP 1510 or 1610 Innovator board support. Say Y here if you - have such a board. + TI OMAP 1510 or 1610 Innovator board support. Say Y here if you + have such a board. config MACH_OMAP_H2 bool "TI H2 Support" depends on ARCH_OMAP1 && ARCH_OMAP16XX - help + help TI OMAP 1610/1611B H2 board support. Say Y here if you have such a board. config MACH_OMAP_H3 bool "TI H3 Support" depends on ARCH_OMAP1 && ARCH_OMAP16XX - help + help TI OMAP 1710 H3 board support. Say Y here if you have such a board.@@ -91,14 +91,14 @@ config MACH_HERALD config MACH_OMAP_OSK bool "TI OSK Support" depends on ARCH_OMAP1 && ARCH_OMAP16XX - help + help TI OMAP 5912 OSK (OMAP Starter Kit) board support. Say Y here - if you have such a board. + if you have such a board. config OMAP_OSK_MISTRAL bool "Mistral QVGA board Support" depends on MACH_OMAP_OSK - help + help The OSK supports an optional add-on board with a Quarter-VGA touchscreen, PDA-ish buttons, a resume button, bicolor LED, and camera connector. Say Y here if you have this board.@@ -106,14 +106,14 @@ config OMAP_OSK_MISTRAL config MACH_OMAP_PERSEUS2 bool "TI Perseus2" depends on ARCH_OMAP1 && ARCH_OMAP730 - help + help Support for TI OMAP 730 Perseus2 board. Say Y here if you have such a board. config MACH_OMAP_FSAMPLE bool "TI F-Sample" depends on ARCH_OMAP1 && ARCH_OMAP730 - help + help Support for TI OMAP 850 F-Sample board. Say Y here if you have such a board.@@ -130,10 +130,10 @@ config MACH_OMAP_PALMZ71 bool "Palm Zire71" depends on ARCH_OMAP1 && ARCH_OMAP15XX help - Support for the Palm Zire71 PDA. To boot the kernel, - you'll need a PalmOS compatible bootloader; check out - http://hackndev.com/palm/z71 for more information. - Say Y here if you have such a PDA, say N otherwise. + Support for the Palm Zire71 PDA. To boot the kernel, + you'll need a PalmOS compatible bootloader; check out + http://hackndev.com/palm/z71 for more information. + Say Y here if you have such a PDA, say N otherwise. config MACH_OMAP_PALMTT bool "Palm Tungsten|T"@@ -179,10 +179,10 @@ config MACH_OMAP_GENERIC bool "Generic OMAP board" depends on ARCH_OMAP1 && (ARCH_OMAP15XX || ARCH_OMAP16XX) help - Support for generic OMAP-1510, 1610 or 1710 board with - no FPGA. Can be used as template for porting Linux to - custom OMAP boards. Say Y here if you have a custom - board. + Support for generic OMAP-1510, 1610 or 1710 board with + no FPGA. Can be used as template for porting Linux to + custom OMAP boards. Say Y here if you have a custom + board. endmenuarch/arm/mach-omap2/Kconfig +6
-6@@ -174,16 +174,16 @@ config SOC_TI81XX default y config OMAP_PACKAGE_CBC - bool + bool config OMAP_PACKAGE_CBB - bool + bool config OMAP_PACKAGE_CUS - bool + bool config OMAP_PACKAGE_CBP - bool + bool comment "OMAP Legacy Platform Data Board Type" depends on ARCH_OMAP2PLUS@@ -208,10 +208,10 @@ config MACH_OMAP3_PANDORA select OMAP_PACKAGE_CBB config MACH_NOKIA_N810 - bool + bool config MACH_NOKIA_N810_WIMAX - bool + bool config MACH_NOKIA_N8X0 bool "Nokia N800/N810"arch/arm/mach-prima2/Kconfig +3
-3@@ -21,7 +21,7 @@ config ARCH_ATLAS6 default y select SIRF_IRQ help - Support for CSR SiRFSoC ARM Cortex A9 Platform + Support for CSR SiRFSoC ARM Cortex A9 Platform config ARCH_ATLAS7 bool "CSR SiRFSoC ATLAS7 ARM Cortex A7 Platform"@@ -31,7 +31,7 @@ config ARCH_ATLAS7 select HAVE_ARM_SCU if SMP select HAVE_SMP help - Support for CSR SiRFSoC ARM Cortex A7 Platform + Support for CSR SiRFSoC ARM Cortex A7 Platform config ARCH_PRIMA2 bool "CSR SiRFSoC PRIMA2 ARM Cortex A9 Platform"@@ -40,7 +40,7 @@ config ARCH_PRIMA2 select ZONE_DMA select PRIMA2_TIMER help - Support for CSR SiRFSoC ARM Cortex A9 Platform + Support for CSR SiRFSoC ARM Cortex A9 Platform config SIRF_IRQ boolarch/arm/mach-s3c24xx/Kconfig +15
-17@@ -17,8 +17,6 @@ config PLAT_S3C24XX help Base platform code for any Samsung S3C24XX device - - menu "SAMSUNG S3C24XX SoCs Support" comment "S3C24XX SoCs"@@ -138,11 +136,11 @@ config S3C2410_IOTIMING and s3c2440/s3c2442 cpu frequency support. config S3C2410_CPUFREQ_UTILS - bool - depends on ARM_S3C24XX_CPUFREQ - help - Internal node to select timing code that is common to the s3c2410 - and s3c2440/s3c244 cpu frequency support. + bool + depends on ARM_S3C24XX_CPUFREQ + help + Internal node to select timing code that is common to the s3c2410 + and s3c2440/s3c244 cpu frequency support. # cpu frequency support common to s3c2412, s3c2413 and s3c2442@@ -280,7 +278,7 @@ config MACH_VR1000 help Say Y here if you are using the Thorcom VR1000 board. -endif # CPU_S3C2410 +endif # CPU_S3C2410 config S3C2412_PM_SLEEP bool@@ -354,7 +352,7 @@ config MACH_VSTMS help Say Y here if you are using an VSTMS board -endif # CPU_S3C2412 +endif # CPU_S3C2412 if CPU_S3C2416@@ -402,7 +400,7 @@ config MACH_S3C2416_DT Note: This is under development and not all peripherals can be supported with this machine file. -endif # CPU_S3C2416 +endif # CPU_S3C2416 if CPU_S3C2440 || CPU_S3C2442@@ -528,7 +526,7 @@ config SMDK2440_CPU2440 default y if ARCH_S3C2440 select S3C2440_XTAL_16934400 -endif # CPU_S3C2440 +endif # CPU_S3C2440 if CPU_S3C2442@@ -548,7 +546,7 @@ config MACH_NEO1973_GTA02 select S3C24XX_PWM select S3C_DEV_USB_HOST help - Say Y here if you are using the Openmoko GTA02 / Freerunner GSM Phone + Say Y here if you are using the Openmoko GTA02 / Freerunner GSM Phone config MACH_RX1950 bool "HP iPAQ rx1950"@@ -560,9 +558,9 @@ config MACH_RX1950 select S3C24XX_PWM select S3C_DEV_NAND help - Say Y here if you're using HP iPAQ rx1950 + Say Y here if you're using HP iPAQ rx1950 -endif # CPU_S3C2442 +endif # CPU_S3C2442 if CPU_S3C2443 || CPU_S3C2416@@ -571,7 +569,7 @@ config S3C2443_SETUP_SPI help Common setup code for SPI GPIO configurations -endif # CPU_S3C2443 || CPU_S3C2416 +endif # CPU_S3C2443 || CPU_S3C2416 if CPU_S3C2443@@ -584,7 +582,7 @@ config MACH_SMDK2443 help Say Y here if you are using an SMDK2443 -endif # CPU_S3C2443 +endif # CPU_S3C2443 config PM_H1940 bool@@ -593,4 +591,4 @@ config PM_H1940 endmenu # SAMSUNG S3C24XX SoCs Support -endif # ARCH_S3C24XX +endif # ARCH_S3C24XXarch/arm/mach-s3c64xx/Kconfig +8
-8@@ -100,7 +100,7 @@ config S3C64XX_SETUP_SDHCI_GPIO config S3C64XX_SETUP_SPI bool help - Common setup code for SPI GPIO configurations + Common setup code for SPI GPIO configurations config S3C64XX_SETUP_USB_PHY bool@@ -110,7 +110,7 @@ config S3C64XX_SETUP_USB_PHY # S36400 Macchine support config MACH_SMDK6400 - bool "SMDK6400" + bool "SMDK6400" depends on ATAGS select CPU_S3C6400 select S3C64XX_SETUP_SDHCI@@ -202,7 +202,7 @@ config SMDK6410_SD_CH0 bool "Use channel 0 only" depends on MACH_SMDK6410 help - Select CON7 (channel 0) as the MMC/SD slot, as + Select CON7 (channel 0) as the MMC/SD slot, as at least some SMDK6410 boards come with the resistors fitted so that the card detects for channels 0 and 1 are the same.@@ -211,7 +211,7 @@ config SMDK6410_SD_CH1 bool "Use channel 1 only" depends on MACH_SMDK6410 help - Select CON6 (channel 1) as the MMC/SD slot, as + Select CON6 (channel 1) as the MMC/SD slot, as at least some SMDK6410 boards come with the resistors fitted so that the card detects for channels 0 and 1 are the same.@@ -257,7 +257,7 @@ config MACH_NCP select S3C_DEV_HSMMC1 select S3C_DEV_I2C1 help - Machine support for the Samsung NCP + Machine support for the Samsung NCP config MACH_HMT bool "Airgoo HMT"@@ -289,21 +289,21 @@ config MACH_SMARTQ select SAMSUNG_DEV_PWM select SAMSUNG_DEV_TS help - Shared machine support for SmartQ 5/7 + Shared machine support for SmartQ 5/7 config MACH_SMARTQ5 bool "SmartQ 5" depends on ATAGS select MACH_SMARTQ help - Machine support for the SmartQ 5 + Machine support for the SmartQ 5 config MACH_SMARTQ7 bool "SmartQ 7" depends on ATAGS select MACH_SMARTQ help - Machine support for the SmartQ 7 + Machine support for the SmartQ 7 config MACH_WLF_CRAGG_6410 bool "Wolfson Cragganmore 6410"arch/arm/mach-sa1100/Kconfig +2
-2@@ -91,8 +91,8 @@ config SA1100_JORNADA720 select SA1111 help Say Y here if you want to build a kernel for the HP Jornada 720 - handheld computer. See - <http://h10025.www1.hp.com/ewfrf/wc/product?product=61677&cc=us&lc=en&dlc=en&product=61677#> + handheld computer. See + <http://h10025.www1.hp.com/ewfrf/wc/product?product=61677&cc=us&lc=en&dlc=en&product=61677#> config SA1100_JORNADA720_SSP bool "HP Jornada 720 Extended SSP driver"arch/arm/mach-vt8500/Kconfig +3
-3@@ -10,9 +10,9 @@ config ARCH_VT8500 config ARCH_WM8505 bool "VIA/Wondermedia 85xx and WM8650" - depends on ARCH_MULTI_V5 - select ARCH_VT8500 - select CPU_ARM926T + depends on ARCH_MULTI_V5 + select ARCH_VT8500 + select CPU_ARM926T config ARCH_WM8750 bool "WonderMedia WM8750"arch/arm/mach-w90x900/Kconfig +3
-3@@ -23,7 +23,7 @@ config MACH_W90P910EVB default y select CPU_W90P910 help - Say Y here if you are using the Nuvoton W90P910EVB + Say Y here if you are using the Nuvoton W90P910EVB endmenu@@ -33,7 +33,7 @@ config MACH_W90P950EVB bool "Nuvoton NUC950 Evaluation Board" select CPU_NUC950 help - Say Y here if you are using the Nuvoton NUC950EVB + Say Y here if you are using the Nuvoton NUC950EVB endmenu@@ -43,7 +43,7 @@ config MACH_W90N960EVB bool "Nuvoton NUC960 Evaluation Board" select CPU_NUC960 help - Say Y here if you are using the Nuvoton NUC960EVB + Say Y here if you are using the Nuvoton NUC960EVB endmenuarch/arm/mm/Kconfig +24
-24@@ -123,13 +123,13 @@ config CPU_ARM925T select CPU_PABRT_LEGACY select CPU_THUMB_CAPABLE select CPU_TLB_V4WBI if MMU - help - The ARM925T is a mix between the ARM920T and ARM926T, but with + help + The ARM925T is a mix between the ARM920T and ARM926T, but with different instruction and data caches. It is used in TI's OMAP - device family. + device family. - Say Y if you want support for the ARM925T processor. - Otherwise, say N. + Say Y if you want support for the ARM925T processor. + Otherwise, say N. # ARM926T config CPU_ARM926T@@ -829,19 +829,19 @@ config HARDEN_BRANCH_PREDICTOR depends on CPU_SPECTRE default y help - Speculation attacks against some high-performance processors rely - on being able to manipulate the branch predictor for a victim - context by executing aliasing branches in the attacker context. - Such attacks can be partially mitigated against by clearing - internal branch predictor state and limiting the prediction - logic in some situations. + Speculation attacks against some high-performance processors rely + on being able to manipulate the branch predictor for a victim + context by executing aliasing branches in the attacker context. + Such attacks can be partially mitigated against by clearing + internal branch predictor state and limiting the prediction + logic in some situations. - This config option will take CPU-specific actions to harden - the branch predictor against aliasing attacks and may rely on - specific instruction sequences or control bits being set by - the system firmware. + This config option will take CPU-specific actions to harden + the branch predictor against aliasing attacks and may rely on + specific instruction sequences or control bits being set by + the system firmware. - If unsure, say Y. + If unsure, say Y. config TLS_REG_EMUL bool@@ -983,14 +983,14 @@ if CACHE_L2X0 config PL310_ERRATA_588369 bool "PL310 errata: Clean & Invalidate maintenance operations do not invalidate clean lines" help - The PL310 L2 cache controller implements three types of Clean & - Invalidate maintenance operations: by Physical Address - (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC). - They are architecturally defined to behave as the execution of a - clean operation followed immediately by an invalidate operation, - both performing to the same memory location. This functionality - is not correctly implemented in PL310 prior to r2p0 (fixed in r2p0) - as clean lines are not invalidated as a result of these operations. + The PL310 L2 cache controller implements three types of Clean & + Invalidate maintenance operations: by Physical Address + (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC). + They are architecturally defined to behave as the execution of a + clean operation followed immediately by an invalidate operation, + both performing to the same memory location. This functionality + is not correctly implemented in PL310 prior to r2p0 (fixed in r2p0) + as clean lines are not invalidated as a result of these operations. config PL310_ERRATA_727915 bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"arch/arm/plat-samsung/Kconfig +13
-14@@ -39,12 +39,12 @@ config SAMSUNG_ATAGS def_bool n depends on ATAGS help - This option enables ATAGS based boot support code for - Samsung platforms, including static platform devices, legacy - clock, timer and interrupt initialization, etc. + This option enables ATAGS based boot support code for + Samsung platforms, including static platform devices, legacy + clock, timer and interrupt initialization, etc. - Platforms that support only DT based boot need not to select - this option. + Platforms that support only DT based boot need not to select + this option. if SAMSUNG_ATAGS@@ -98,7 +98,7 @@ config S3C_DEV_HSMMC3 config S3C_DEV_HWMON bool help - Compile in platform device definitions for HWMON + Compile in platform device definitions for HWMON config S3C_DEV_I2C1 bool@@ -202,7 +202,7 @@ config S3C64XX_DEV_SPI2 config SAMSUNG_DEV_TS bool help - Common in platform device definitions for touchscreen device + Common in platform device definitions for touchscreen device config SAMSUNG_DEV_KEYPAD bool@@ -247,13 +247,13 @@ config SAMSUNG_PM_DEBUG for more information. config S3C_PM_DEBUG_LED_SMDK - bool "SMDK LED suspend/resume debugging" - depends on PM && (MACH_SMDK6410) - help - Say Y here to enable the use of the SMDK LEDs on the baseboard - for debugging of the state of the suspend and resume process. + bool "SMDK LED suspend/resume debugging" + depends on PM && (MACH_SMDK6410) + help + Say Y here to enable the use of the SMDK LEDs on the baseboard + for debugging of the state of the suspend and resume process. - Note, this currently only works for S3C64XX based SMDK boards. + Note, this currently only works for S3C64XX based SMDK boards. config SAMSUNG_PM_CHECK bool "S3C2410 PM Suspend Memory CRC" --1.9.1
Signature · 2 lines
Best Regards Masahiro Yamada
Re: [PATCH 034/114] arch: arm: Kconfig: pedantic formatting
Quoted 6 lines · Masahiro Yamada
Quoted 4 lines · metux IT consult
Formatting of
Kconfigfiles doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
Quoted 8 lines
Quoted 3 lines
Signed-off-by Enrico Weigelt, metux IT consult <[email protected]>--- arch/arm/Kconfig | 24 +++++++++++-----------While you are touching this file,
why don't fix checkpatch.pl warning?
I actually was about changing that, too. But I was a bit confused by the documentation implying this still has some semantics. Personally, I'd prefer changing everything to "help".
--mtx
Signature · 3 lines
Enrico Weigelt, metux IT consult Free software and Linux embedded engineering [email protected] -- +49-151-27565287
PATCH 35/114 arch: arc: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/arc/Kconfig | 12 ++++++------ arch/arc/plat-eznps/Kconfig | 12 ++++++------ 2 files changed, 12 insertions(+), 12 deletions(-)
arch/arc/Kconfig +6 -6
@@ -144,11 +144,11 @@ config ARC_CPU_770 Support for ARC770 core introduced with Rel 4.10 (Summer 2011) This core has a bunch of cool new features: -MMU-v3: Variable Page Sz (4k, 8k, 16k), bigger J-TLB (128x4) - Shared Address Spaces (for sharing TLB entries in MMU) + Shared Address Spaces (for sharing TLB entries in MMU) -Caches: New Prog Model, Region Flush -Insns: endian swap, load-locked/store-conditional, time-stamp-ctr -endif #ISA_ARCOMPACT +endif #ISA_ARCOMPACT config ARC_CPU_HS bool "ARC-HS"
@@ -198,7 +198,7 @@ config ARC_SMP_HALT_ON_RESET at designated entry point. For other case, all jump to common entry point and spin wait for Master's signal. -endif #SMP +endif #SMP config ARC_MCIP bool "ARConnect Multicore IP (MCIP) Support "
@@ -249,7 +249,7 @@ config ARC_CACHE_VIPT_ALIASING bool "Support VIPT Aliasing D$" depends on ARC_HAS_DCACHE && ISA_ARCOMPACT -endif #ARC_CACHE +endif #ARC_CACHE config ARC_HAS_ICCM bool "Use ICCM"
@@ -370,7 +370,7 @@ config ARC_FPU_SAVE_RESTORE based on actual usage of FPU by a task. Thus our implemn does this for all tasks in system. -endif #ISA_ARCOMPACT +endif #ISA_ARCOMPACT config ARC_CANT_LLSC def_bool n
@@ -414,7 +414,7 @@ config ARC_IRQ_NO_AUTOSAVE This is programmable and can be optionally disabled in which case software INTERRUPT_PROLOGUE/EPILGUE do the needed work -endif # ISA_ARCV2 +endif # ISA_ARCV2 endmenu # "ARC CPU Configuration"
arch/arc/plat-eznps/Kconfig +6 -6
@@ -26,8 +26,8 @@ config EZNPS_MTM_EXT help Here we add new hierarchy for CPUs topology. We got: - Core - Thread + Core + Thread At the new thread level each CPU represent one HW thread. At highest hierarchy each core contain 16 threads, any of them seem like CPU from Linux point of view.
@@ -35,10 +35,10 @@ config EZNPS_MTM_EXT core and HW scheduler round robin between them. config EZNPS_MEM_ERROR_ALIGN - bool "ARC-EZchip Memory error as an exception" - depends on EZNPS_MTM_EXT - default n - help + bool "ARC-EZchip Memory error as an exception" + depends on EZNPS_MTM_EXT + default n + help On the real chip of the NPS, user memory errors are handled as a machine check exception, which is fatal, whereas on simulator platform for NPS, is handled as a Level 2 interrupt
Signature · 1 line
1.9.1
PATCH 36/114 arch: amd64: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/arm64/Kconfig | 58 +++++++++++++++++++++++++------------------------- arch/arm64/kvm/Kconfig | 2 +- 2 files changed, 30 insertions(+), 30 deletions(-)
arch/arm64/Kconfig +29 -29
@@ -196,31 +196,31 @@ config ARM64_CONT_SHIFT default 4 config ARCH_MMAP_RND_BITS_MIN - default 14 if ARM64_64K_PAGES - default 16 if ARM64_16K_PAGES - default 18 + default 14 if ARM64_64K_PAGES + default 16 if ARM64_16K_PAGES + default 18 # max bits determined by the following formula: # VA_BITS - PAGE_SHIFT - 3 config ARCH_MMAP_RND_BITS_MAX - default 19 if ARM64_VA_BITS=36 - default 24 if ARM64_VA_BITS=39 - default 27 if ARM64_VA_BITS=42 - default 30 if ARM64_VA_BITS=47 - default 29 if ARM64_VA_BITS=48 && ARM64_64K_PAGES - default 31 if ARM64_VA_BITS=48 && ARM64_16K_PAGES - default 33 if ARM64_VA_BITS=48 - default 14 if ARM64_64K_PAGES - default 16 if ARM64_16K_PAGES - default 18 + default 19 if ARM64_VA_BITS=36 + default 24 if ARM64_VA_BITS=39 + default 27 if ARM64_VA_BITS=42 + default 30 if ARM64_VA_BITS=47 + default 29 if ARM64_VA_BITS=48 && ARM64_64K_PAGES + default 31 if ARM64_VA_BITS=48 && ARM64_16K_PAGES + default 33 if ARM64_VA_BITS=48 + default 14 if ARM64_64K_PAGES + default 16 if ARM64_16K_PAGES + default 18 config ARCH_MMAP_RND_COMPAT_BITS_MIN - default 7 if ARM64_64K_PAGES - default 9 if ARM64_16K_PAGES - default 11 + default 7 if ARM64_64K_PAGES + default 9 if ARM64_16K_PAGES + default 11 config ARCH_MMAP_RND_COMPAT_BITS_MAX - default 16 + default 16 config NO_IOPORT_MAP def_bool y if !PCI
@@ -253,7 +253,7 @@ config GENERIC_HWEIGHT def_bool y config GENERIC_CSUM - def_bool y + def_bool y config GENERIC_CALIBRATE_DELAY def_bool y
@@ -790,9 +790,9 @@ config ARM64_PA_BITS default 52 if ARM64_PA_BITS_52 config CPU_BIG_ENDIAN - bool "Build big-endian kernel" - help - Say Y if you plan on running a kernel in big-endian mode. + bool "Build big-endian kernel" + help + Say Y if you plan on running a kernel in big-endian mode. config SCHED_MC bool "Multi-core scheduler support"
@@ -1178,15 +1178,15 @@ config ARM64_PAN bool "Enable support for Privileged Access Never (PAN)" default y help - Privileged Access Never (PAN; part of the ARMv8.1 Extensions) - prevents the kernel or hypervisor from accessing user-space (EL0) - memory directly. + Privileged Access Never (PAN; part of the ARMv8.1 Extensions) + prevents the kernel or hypervisor from accessing user-space (EL0) + memory directly. - Choosing this option will cause any unprotected (not using - copy_to_user et al) memory access to fail with a permission fault. + Choosing this option will cause any unprotected (not using + copy_to_user et al) memory access to fail with a permission fault. - The feature is detected at runtime, and will remain as a 'nop' - instruction if the cpu does not implement the feature. + The feature is detected at runtime, and will remain as a 'nop' + instruction if the cpu does not implement the feature. config ARM64_LSE_ATOMICS bool "Atomic instructions"
@@ -1459,7 +1459,7 @@ config EFI help This option provides support for runtime services provided by UEFI firmware (such as non-volatile variables, realtime - clock, and platform reset). A UEFI stub is also provided to + clock, and platform reset). A UEFI stub is also provided to allow the kernel to be booted as an EFI application. This is only useful on systems that have UEFI firmware.
arch/arm64/kvm/Kconfig +1 -1
@@ -59,7 +59,7 @@ config KVM_ARM_PMU virtual machines. config KVM_INDIRECT_VECTORS - def_bool KVM && (HARDEN_BRANCH_PREDICTOR || HARDEN_EL2_VECTORS) + def_bool KVM && (HARDEN_BRANCH_PREDICTOR || HARDEN_EL2_VECTORS) source "drivers/vhost/Kconfig"
Signature · 1 line
1.9.1
PATCH 37/114 arch: powerpc: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/powerpc/Kconfig | 28 ++++++++++++++-------------- arch/powerpc/kvm/Kconfig | 6 +++--- arch/powerpc/platforms/40x/Kconfig | 7 +++---- arch/powerpc/platforms/44x/Kconfig | 10 +++++----- arch/powerpc/platforms/85xx/Kconfig | 8 ++++---- arch/powerpc/platforms/86xx/Kconfig | 6 +++--- arch/powerpc/platforms/maple/Kconfig | 2 +- arch/powerpc/platforms/pseries/Kconfig | 18 +++++++++--------- arch/powerpc/sysdev/xics/Kconfig | 13 ++++++------- 9 files changed, 48 insertions(+), 50 deletions(-)
arch/powerpc/Kconfig +14 -14
@@ -48,7 +48,7 @@ config ARCH_MMAP_RND_COMPAT_BITS_MAX # Allow randomisation to consume up to 512MB of address space (2^29). default 11 if PPC_256K_PAGES # 11 = 29 (512MB) - 18 (256K) default 13 if PPC_64K_PAGES # 13 = 29 (512MB) - 16 (64K) - default 15 if PPC_16K_PAGES # 15 = 29 (512MB) - 14 (16K) + default 15 if PPC_16K_PAGES # 15 = 29 (512MB) - 14 (16K) default 17 # 17 = 29 (512MB) - 12 (4K) config ARCH_MMAP_RND_COMPAT_BITS_MIN
@@ -246,9 +246,9 @@ config PPC # config PPC_BARRIER_NOSPEC - bool - default y - depends on PPC_BOOK3S_64 || PPC_FSL_BOOK3E + bool + default y + depends on PPC_BOOK3S_64 || PPC_FSL_BOOK3E config EARLY_PRINTK bool
@@ -430,13 +430,13 @@ config MATH_EMULATION_HW_UNIMPLEMENTED endchoice config PPC_TRANSACTIONAL_MEM - bool "Transactional Memory support for POWERPC" - depends on PPC_BOOK3S_64 - depends on SMP - select ALTIVEC - select VSX - ---help--- - Support user-mode Transactional Memory on POWERPC. + bool "Transactional Memory support for POWERPC" + depends on PPC_BOOK3S_64 + depends on SMP + select ALTIVEC + select VSX + ---help--- + Support user-mode Transactional Memory on POWERPC. config LD_HEAD_STUB_CATCH bool "Reserve 256 bytes to cope with linker stubs in HEAD text" if EXPERT
@@ -937,7 +937,7 @@ config FSL_SOC bool config FSL_PCI - bool + bool select ARCH_HAS_DMA_SET_MASK select PPC_INDIRECT_PCI select PCI_QUIRKS
@@ -1049,14 +1049,14 @@ config DYNAMIC_MEMSTART select NONSTATIC_KERNEL help This option enables the kernel to be loaded at any page aligned - physical address. The kernel creates a mapping from KERNELBASE to + physical address. The kernel creates a mapping from KERNELBASE to the address where the kernel is loaded. The page size here implies the TLB page size of the mapping for kernel on the particular platform. Please refer to the init code for finding the TLB page size. DYNAMIC_MEMSTART is an easy way of implementing pseudo-RELOCATABLE kernel image, where the only restriction is the page aligned kernel - load address. When this option is enabled, the compile time physical + load address. When this option is enabled, the compile time physical address CONFIG_PHYSICAL_START is ignored. This option is overridden by CONFIG_RELOCATABLE
arch/powerpc/kvm/Kconfig +3 -3
@@ -184,9 +184,9 @@ config KVM_MPIC select HAVE_KVM_MSI help Enable support for emulating MPIC devices inside the - host kernel, rather than relying on userspace to emulate. - Currently, support is limited to certain versions of - Freescale's MPIC implementation. + host kernel, rather than relying on userspace to emulate. + Currently, support is limited to certain versions of + Freescale's MPIC implementation. config KVM_XICS bool "KVM in-kernel XICS emulation"
arch/powerpc/platforms/40x/Kconfig +3 -4
@@ -16,12 +16,12 @@ config EP405 This option enables support for the EP405/EP405PC boards. config HOTFOOT - bool "Hotfoot" + bool "Hotfoot" depends on 40x select PPC40x_SIMPLE select FORCE_PCI - help - This option enables support for the ESTEEM 195E Hotfoot board. + help + This option enables support for the ESTEEM 195E Hotfoot board. config KILAUEA bool "Kilauea"
@@ -80,7 +80,6 @@ config OBS600 help This option enables support for PlatHome OpenBlockS 600 server - config PPC40x_SIMPLE bool "Simple PowerPC 40x board support" depends on 40x
arch/powerpc/platforms/44x/Kconfig +5 -5
@@ -40,12 +40,12 @@ config EBONY This option enables support for the IBM PPC440GP evaluation board. config SAM440EP - bool "Sam440ep" + bool "Sam440ep" depends on 44x - select 440EP - select FORCE_PCI - help - This option enables support for the ACube Sam440ep board. + select 440EP + select FORCE_PCI + help + This option enables support for the ACube Sam440ep board. config SEQUOIA bool "Sequoia"
arch/powerpc/platforms/85xx/Kconfig +4 -4
@@ -147,10 +147,10 @@ config SOCRATES This option enables support for the Socrates board. config KSI8560 - bool "Emerson KSI8560" - select DEFAULT_UIMAGE - help - This option enables support for the Emerson KSI8560 board + bool "Emerson KSI8560" + select DEFAULT_UIMAGE + help + This option enables support for the Emerson KSI8560 board config XES_MPC85xx bool "X-ES single-board computer"
arch/powerpc/platforms/86xx/Kconfig +3 -3
@@ -62,9 +62,9 @@ config GEF_SBC610 This option enables support for the GE SBC610. config MVME7100 - bool "Artesyn MVME7100" - help - This option enables support for the Emerson/Artesyn MVME7100 board. + bool "Artesyn MVME7100" + help + This option enables support for the Emerson/Artesyn MVME7100 board. endif
arch/powerpc/platforms/maple/Kconfig +1 -1
@@ -14,5 +14,5 @@ config PPC_MAPLE select MMIO_NVRAM select ATA_NONSTANDARD if ATA help - This option enables support for the Maple 970FX Evaluation Board. + This option enables support for the Maple 970FX Evaluation Board. For more information, refer to <http://www.970eval.com>
arch/powerpc/platforms/pseries/Kconfig +9 -9
@@ -80,19 +80,19 @@ config LPARCFG bool "LPAR Configuration Data" depends on PPC_PSERIES help - Provide system capacity information via human readable - <key word>=<value> pairs through a /proc/ppc64/lparcfg interface. + Provide system capacity information via human readable + <key word>=<value> pairs through a /proc/ppc64/lparcfg interface. config PPC_PSERIES_DEBUG depends on PPC_PSERIES && PPC_EARLY_DEBUG bool "Enable extra debug logging in platforms/pseries" - help + default y + help Say Y here if you want the pseries core to produce a bunch of debug messages to the system log. Select this if you are having a problem with the pseries core and want to see more of what is going on. This does not enable debugging in lpar.c, which must be manually done due to its verbosity. - default y config PPC_SMLPAR bool "Support for shared-memory logical partitions"
@@ -117,16 +117,16 @@ config CMM balance memory across many LPARs. config HV_PERF_CTRS - bool "Hypervisor supplied PMU events (24x7 & GPCI)" - default y - depends on PERF_EVENTS && PPC_PSERIES - help + bool "Hypervisor supplied PMU events (24x7 & GPCI)" + default y + depends on PERF_EVENTS && PPC_PSERIES + help Enable access to hypervisor supplied counters in perf. Currently, this enables code that uses the hcall GetPerfCounterInfo and 24x7 interfaces to retrieve counters. GPCI exists on Power 6 and later systems. 24x7 is available on Power 8 and later systems. - If unsure, select Y. + If unsure, select Y. config IBMVIO depends on PPC_PSERIES
arch/powerpc/sysdev/xics/Kconfig +6 -7
@@ -1,15 +1,14 @@ # SPDX-License-Identifier: GPL-2.0 config PPC_XICS - def_bool n - select PPC_SMP_MUXED_IPI - select HARDIRQS_SW_RESEND + def_bool n + select PPC_SMP_MUXED_IPI + select HARDIRQS_SW_RESEND config PPC_ICP_NATIVE - def_bool n + def_bool n config PPC_ICP_HV - def_bool n + def_bool n config PPC_ICS_RTAS - def_bool n - + def_bool n
Signature · 1 line
1.9.1
Michael Ellerman
reviewerRe: [PATCH 037/114] arch: powerpc: Kconfig: pedantic formatting
Quoted 28 lines · metux IT consult
Formatting of
Kconfigfiles doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.Signed-off-by Enrico Weigelt, metux IT consult <[email protected]>--- arch/powerpc/Kconfig | 28 ++++++++++++++-------------- arch/powerpc/kvm/Kconfig | 6 +++--- arch/powerpc/platforms/40x/Kconfig | 7 +++---- arch/powerpc/platforms/44x/Kconfig | 10 +++++----- arch/powerpc/platforms/85xx/Kconfig | 8 ++++---- arch/powerpc/platforms/86xx/Kconfig | 6 +++--- arch/powerpc/platforms/maple/Kconfig | 2 +- arch/powerpc/platforms/pseries/Kconfig | 18 +++++++++--------- arch/powerpc/sysdev/xics/Kconfig | 13 ++++++------- 9 files changed, 48 insertions(+), 50 deletions(-)arch/powerpc/Kconfig +0
-4@@ -430,13 +430,13 @@ config MATH_EMULATION_HW_UNIMPLEMENTED endchoice config PPC_TRANSACTIONAL_MEM - bool "Transactional Memory support for POWERPC" - depends on PPC_BOOK3S_64 - depends on SMP - select ALTIVEC
arch/powerpc/Kconfig config MATH_EMULATION_HW_UNIMPLEMENTED · line 439
Quoted 10 lines
arch/powerpc/Kconfig +7
-3- select VSX - ---help--- - Support user-mode Transactional Memory on POWERPC. + bool "Transactional Memory support for POWERPC" + depends on PPC_BOOK3S_64 + depends on SMP + select ALTIVEC + select VSX + ---help--- + Support user-mode Transactional Memory on POWERPC.
If you're going to do this can you also convert all the "---help---" instances to just "help"? Thanks.
cheers
PATCH 38/114 arch: mips: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/mips/Kconfig | 61 ++++++++++++++++++++-------------------- arch/mips/bcm47xx/Kconfig | 8 +++--- arch/mips/bcm63xx/boards/Kconfig | 2 +- arch/mips/pic32/Kconfig | 8 +++--- 4 files changed, 39 insertions(+), 40 deletions(-)
arch/mips/Kconfig +30 -31
@@ -276,7 +276,7 @@ config BCM47XX select BCM47XX_SPROM select BCM47XX_SSB if !BCM47XX_BCMA help - Support for BCM47XX based boards + Support for BCM47XX based boards config BCM63XX bool "Broadcom BCM63XX based boards"
@@ -295,7 +295,7 @@ config BCM63XX select MIPS_L1_CACHE_SHIFT_4 select CLKDEV_LOOKUP help - Support for BCM63XX based boards + Support for BCM63XX based boards config MIPS_COBALT bool "Cobalt Server"
@@ -374,10 +374,10 @@ config MACH_JAZZ select SYS_SUPPORTS_64BIT_KERNEL select SYS_SUPPORTS_100HZ help - This a family of machines based on the MIPS R4030 chipset which was - used by several vendors to build RISC/os and Windows NT workstations. - Members include the Acer PICA, MIPS Magnum 4000, MIPS Millennium and - Olivetti M700-10 workstations. + This a family of machines based on the MIPS R4030 chipset which was + used by several vendors to build RISC/os and Windows NT workstations. + Members include the Acer PICA, MIPS Magnum 4000, MIPS Millennium and + Olivetti M700-10 workstations. config MACH_INGENIC bool "Ingenic SoC based machines"
@@ -573,14 +573,14 @@ config NXP_STB220 bool "NXP STB220 board" select SOC_PNX833X help - Support for NXP Semiconductors STB220 Development Board. + Support for NXP Semiconductors STB220 Development Board. config NXP_STB225 bool "NXP 225 board" select SOC_PNX833X select SOC_PNX8335 help - Support for NXP Semiconductors STB225 Development Board. + Support for NXP Semiconductors STB225 Development Board. config PMC_MSP bool "PMC-Sierra MSP chipsets"
@@ -722,9 +722,9 @@ config SGI_IP28 select SYS_SUPPORTS_64BIT_KERNEL select SYS_SUPPORTS_BIG_ENDIAN select MIPS_L1_CACHE_SHIFT_7 - help - This is the SGI Indigo2 with R10000 processor. To compile a Linux - kernel that runs on these, say Y here. + help + This is the SGI Indigo2 with R10000 processor. To compile a Linux + kernel that runs on these, say Y here. config SGI_IP32 bool "SGI IP32 (O2)"
@@ -1175,9 +1175,9 @@ config HOLES_IN_ZONE config SYS_SUPPORTS_RELOCATABLE bool help - Selected if the platform supports relocating the kernel. - The platform must provide plat_get_fdt() if it selects CONFIG_USE_OF - to allow access to command line and entropy sources. + Selected if the platform supports relocating the kernel. + The platform must provide plat_get_fdt() if it selects CONFIG_USE_OF + to allow access to command line and entropy sources. config MIPS_CBPF_JIT def_bool y
@@ -2120,8 +2120,8 @@ config MIPS_PGD_C0_CONTEXT # Set to y for ptrace access to watch registers. # config HARDWARE_WATCHPOINTS - bool - default y if CPU_MIPSR1 || CPU_MIPSR2 || CPU_MIPSR6 + bool + default y if CPU_MIPSR1 || CPU_MIPSR2 || CPU_MIPSR6 menu "Kernel type"
@@ -2185,10 +2185,10 @@ config PAGE_SIZE_4KB bool "4kB" depends on !CPU_LOONGSON2 && !CPU_LOONGSON3 help - This option select the standard 4kB Linux page size. On some - R3000-family processors this is the only available page size. Using - 4kB page size will minimize memory consumption and is therefore - recommended for low memory systems. + This option select the standard 4kB Linux page size. On some + R3000-family processors this is the only available page size. Using + 4kB page size will minimize memory consumption and is therefore + recommended for low memory systems. config PAGE_SIZE_8KB bool "8kB"
@@ -2481,7 +2481,6 @@ config SB1_PASS_2_1_WORKAROUNDS depends on CPU_SB1 && CPU_SB1_PASS_2 default y - choice prompt "SmartMIPS or microMIPS ASE support"
@@ -2689,16 +2688,16 @@ config RANDOMIZE_BASE bool "Randomize the address of the kernel image" depends on RELOCATABLE ---help--- - Randomizes the physical and virtual address at which the - kernel image is loaded, as a security feature that - deters exploit attempts relying on knowledge of the location - of kernel internals. + Randomizes the physical and virtual address at which the + kernel image is loaded, as a security feature that + deters exploit attempts relying on knowledge of the location + of kernel internals. - Entropy is generated using any coprocessor 0 registers available. + Entropy is generated using any coprocessor 0 registers available. - The kernel will be offset by up to RANDOMIZE_BASE_MAX_OFFSET. + The kernel will be offset by up to RANDOMIZE_BASE_MAX_OFFSET. - If unsure, say N. + If unsure, say N. config RANDOMIZE_BASE_MAX_OFFSET hex "Maximum kASLR offset" if EXPERT
@@ -2828,7 +2827,7 @@ choice prompt "Timer frequency" default HZ_250 help - Allows the configuration of the timer frequency. + Allows the configuration of the timer frequency. config HZ_24 bool "24 HZ" if SYS_SUPPORTS_24HZ || SYS_SUPPORTS_ARBIT_HZ
@@ -3128,10 +3127,10 @@ config ARCH_MMAP_RND_BITS_MAX default 15 config ARCH_MMAP_RND_COMPAT_BITS_MIN - default 8 + default 8 config ARCH_MMAP_RND_COMPAT_BITS_MAX - default 15 + default 15 config I8253 bool
arch/mips/bcm47xx/Kconfig +4 -4
@@ -15,9 +15,9 @@ config BCM47XX_SSB select SSB_DRIVER_GPIO default y help - Add support for old Broadcom BCM47xx boards with Sonics Silicon Backplane support. + Add support for old Broadcom BCM47xx boards with Sonics Silicon Backplane support. - This will generate an image with support for SSB and MIPS32 R1 instruction set. + This will generate an image with support for SSB and MIPS32 R1 instruction set. config BCM47XX_BCMA bool "BCMA Support for Broadcom BCM47XX"
@@ -31,8 +31,8 @@ config BCM47XX_BCMA select BCMA_DRIVER_GPIO default y help - Add support for new Broadcom BCM47xx boards with Broadcom specific Advanced Microcontroller Bus. + Add support for new Broadcom BCM47xx boards with Broadcom specific Advanced Microcontroller Bus. - This will generate an image with support for BCMA and MIPS32 R2 instruction set. + This will generate an image with support for BCMA and MIPS32 R2 instruction set. endif
arch/mips/bcm63xx/boards/Kconfig +1 -1
@@ -5,7 +5,7 @@ choice default BOARD_BCM963XX config BOARD_BCM963XX - bool "Generic Broadcom 963xx boards" + bool "Generic Broadcom 963xx boards" select SSB endchoice
arch/mips/pic32/Kconfig +4 -4
@@ -39,12 +39,12 @@ choice Select the devicetree. config DTB_PIC32_NONE - bool "None" + bool "None" config DTB_PIC32_MZDA_SK - bool "PIC32MZDA Starter Kit" - depends on PIC32MZDA - select BUILTIN_DTB + bool "PIC32MZDA Starter Kit" + depends on PIC32MZDA + select BUILTIN_DTB endchoice
Signature · 1 line
1.9.1
PATCH 39/114 drivers: video: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/video/Kconfig | 5 +- drivers/video/backlight/Kconfig | 28 ++++----- drivers/video/console/Kconfig | 135 ++++++++++++++++++++-------------------- 3 files changed, 83 insertions(+), 85 deletions(-)
drivers/video/Kconfig +2 -3
@@ -25,8 +25,8 @@ endmenu source "drivers/video/backlight/Kconfig" config VGASTATE - tristate - default n + tristate + default n config VIDEOMODE_HELPERS bool
@@ -45,5 +45,4 @@ if FB || SGI_NEWPORT_CONSOLE endif - endmenu
drivers/video/backlight/Kconfig +14 -14
@@ -14,7 +14,7 @@ if BACKLIGHT_LCD_SUPPORT # LCD # config LCD_CLASS_DEVICE - tristate "Lowlevel LCD controls" + tristate "Lowlevel LCD controls" default m help This framework adds support for low-level control of LCD.
@@ -134,12 +134,12 @@ config LCD_HX8357 If you have a HX-8357 LCD panel, say Y to enable its LCD control driver. - config LCD_OTM3225A - tristate "ORISE Technology OTM3225A support" - depends on SPI - help - If you have a panel based on the OTM3225A controller - chip then say y to include a driver for it. +config LCD_OTM3225A + tristate "ORISE Technology OTM3225A support" + depends on SPI + help + If you have a panel based on the OTM3225A controller + chip then say y to include a driver for it. endif # LCD_CLASS_DEVICE
@@ -147,11 +147,11 @@ endif # LCD_CLASS_DEVICE # Backlight # config BACKLIGHT_CLASS_DEVICE - tristate "Lowlevel Backlight controls" + tristate "Lowlevel Backlight controls" default m help This framework adds support for low-level control of the LCD - backlight. This includes support for brightness and power. + backlight. This includes support for brightness and power. To have support for your specific LCD panel you will have to select the proper drivers which depend on this option.
@@ -277,11 +277,11 @@ config BACKLIGHT_MAX8925 WLED output, say Y here to enable this driver. config BACKLIGHT_APPLE - tristate "Apple Backlight Driver" - depends on X86 && ACPI - help - If you have an Intel-based Apple say Y to enable a driver for its - backlight. + tristate "Apple Backlight Driver" + depends on X86 && ACPI + help + If you have an Intel-based Apple say Y to enable a driver for its + backlight. config BACKLIGHT_TOSA tristate "Sharp SL-6000 Backlight Driver"
drivers/video/console/Kconfig +67 -68
174 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH 40/114 drivers: usb: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/usb/Kconfig | 2 +- drivers/usb/atm/Kconfig | 2 +- drivers/usb/dwc3/Kconfig | 14 +-- drivers/usb/gadget/Kconfig | 160 +++++++++++++------------- drivers/usb/gadget/legacy/Kconfig | 48 ++++---- drivers/usb/gadget/udc/Kconfig | 234 +++++++++++++++++++------------------- drivers/usb/host/Kconfig | 120 +++++++++---------- drivers/usb/misc/Kconfig | 32 +++--- drivers/usb/serial/Kconfig | 60 +++++----- drivers/usb/wusbcore/Kconfig | 13 +-- 10 files changed, 342 insertions(+), 343 deletions(-)
drivers/usb/Kconfig +1 -1
@@ -53,7 +53,7 @@ config USB traditional PC serial port. The bus supplies power to peripherals and allows for hot swapping. Up to 127 USB peripherals can be connected to a single USB host in a tree structure. - + The USB host is the root of the tree, the peripherals are the leaves and the inner nodes are special USB devices called hubs. Most PCs now have USB host ports, used to connect peripherals
drivers/usb/atm/Kconfig +1 -1
@@ -23,7 +23,7 @@ config USB_SPEEDTOUCH select FW_LOADER help Say Y here if you have an SpeedTouch USB or SpeedTouch 330 - modem. In order to use your modem you will need to install the + modem. In order to use your modem you will need to install the two parts of the firmware, extracted by the user space tools; see <http://www.linux-usb.org/SpeedTouch/> for details.
drivers/usb/dwc3/Kconfig +7 -7
@@ -96,13 +96,13 @@ config USB_DWC3_KEYSTONE Say 'Y' or 'M' here if you have one such device config USB_DWC3_OF_SIMPLE - tristate "Generic OF Simple Glue Layer" - depends on OF && COMMON_CLK - default USB_DWC3 - help - Support USB2/3 functionality in simple SoC integrations. - Currently supports Xilinx and Qualcomm DWC USB3 IP. - Say 'Y' or 'M' if you have one such device. + tristate "Generic OF Simple Glue Layer" + depends on OF && COMMON_CLK + default USB_DWC3 + help + Support USB2/3 functionality in simple SoC integrations. + Currently supports Xilinx and Qualcomm DWC USB3 IP. + Say 'Y' or 'M' if you have one such device. config USB_DWC3_ST tristate "STMicroelectronics Platforms"
drivers/usb/gadget/Kconfig +80 -80
214 lines not on this page · raw message
drivers/usb/gadget/legacy/Kconfig +24 -24
60 lines not on this page · raw message
drivers/usb/gadget/udc/Kconfig +117 -117
356 lines not on this page · raw message
drivers/usb/host/Kconfig +60 -60
206 lines not on this page · raw message
drivers/usb/misc/Kconfig +16 -16
@@ -99,7 +99,7 @@ config USB_CYTHERM Say Y here if you want to connect a Cypress USB thermometer device to your computer's USB port. This device is also known as the Cypress USB Starter kit or demo board. The Elektor - magazine published a modified version of this device in issue + magazine published a modified version of this device in issue #291. To compile this driver as a module, choose M here: the
@@ -173,10 +173,10 @@ config USB_IOWARRIOR help Say Y here if you want to support the IO Warrior devices from Code Mercenaries. This includes support for the following devices: - IO Warrior 40 - IO Warrior 24 - IO Warrior 56 - IO Warrior 24 Power Vampire + IO Warrior 40 + IO Warrior 24 + IO Warrior 56 + IO Warrior 24 Power Vampire To compile this driver as a module, choose M here: the module will be called iowarrior.
@@ -192,8 +192,8 @@ config USB_TEST including sample test device firmware and "how to use it". config USB_EHSET_TEST_FIXTURE - tristate "USB EHSET Test Fixture driver" - help + tristate "USB EHSET Test Fixture driver" + help Say Y here if you want to support the special test fixture device used for the USB-IF Embedded Host High-Speed Electrical Test procedure.
@@ -244,17 +244,17 @@ config USB_HUB_USB251XB Say Y or M here if you need to configure such a device via SMBus. config USB_HSIC_USB3503 - tristate "USB3503 HSIC to USB20 Driver" - depends on I2C - select REGMAP_I2C - help - This option enables support for SMSC USB3503 HSIC to USB 2.0 Driver. + tristate "USB3503 HSIC to USB20 Driver" + depends on I2C + select REGMAP_I2C + help + This option enables support for SMSC USB3503 HSIC to USB 2.0 Driver. config USB_HSIC_USB4604 - tristate "USB4604 HSIC to USB20 Driver" - depends on I2C - help - This option enables support for SMSC USB4604 HSIC to USB 2.0 Driver. + tristate "USB4604 HSIC to USB20 Driver" + depends on I2C + help + This option enables support for SMSC USB4604 HSIC to USB 2.0 Driver. config USB_LINK_LAYER_TEST tristate "USB Link Layer Test driver"
drivers/usb/serial/Kconfig +30 -30
95 lines not on this page · raw message
drivers/usb/wusbcore/Kconfig +6 -7
@@ -5,15 +5,15 @@ config USB_WUSB tristate "Enable Wireless USB extensions" depends on UWB - select CRYPTO - select CRYPTO_BLKCIPHER - select CRYPTO_CBC - select CRYPTO_MANAGER - select CRYPTO_AES + select CRYPTO + select CRYPTO_BLKCIPHER + select CRYPTO_CBC + select CRYPTO_MANAGER + select CRYPTO_AES help Enable the host-side support for Wireless USB. - To compile this support select Y (built in). It is safe to + To compile this support select Y (built in). It is safe to select even if you don't have the hardware. config USB_WUSB_CBAF
@@ -37,4 +37,3 @@ config USB_WUSB_CBAF_DEBUG Say Y here if you want the CBA to produce a bunch of debug messages to the system log. Select this if you are having a problem with CBA support and want to see more of what is going on. -
Signature · 1 line
1.9.1
PATCH 41/114 drivers: w1: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/w1/masters/Kconfig | 7 +++---- drivers/w1/slaves/Kconfig | 4 ++-- 2 files changed, 5 insertions(+), 6 deletions(-)
drivers/w1/masters/Kconfig +3 -4
@@ -16,12 +16,12 @@ config W1_MASTER_MATROX config W1_MASTER_DS2490 tristate "DS2490 USB <-> W1 transport layer for 1-wire" - depends on USB - help + depends on USB + help Say Y here if you want to have a driver for DS2490 based USB <-> W1 bridges, for example DS9490*. - This support is also available as a module. If so, the module + This support is also available as a module. If so, the module will be called ds2490. config W1_MASTER_DS2482
@@ -65,4 +65,3 @@ config HDQ_MASTER_OMAP on an OMAP processor. endmenu -
drivers/w1/slaves/Kconfig +2 -2
@@ -70,8 +70,8 @@ config W1_SLAVE_DS2805 help Say Y here if you want to use a 1-wire is a 112-byte user-programmable EEPROM is - organized as 7 pages of 16 bytes each with 64bit - unique number. Requires OverDrive Speed to talk to. + organized as 7 pages of 16 bytes each with 64bit + unique number. Requires OverDrive Speed to talk to. config W1_SLAVE_DS2431 tristate "1kb EEPROM family support (DS2431)"
Signature · 1 line
1.9.1
PATCH 42/114 drivers: tty: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/tty/Kconfig | 45 ++++++++------- drivers/tty/hvc/Kconfig | 30 +++++----- drivers/tty/serial/8250/Kconfig | 4 +- drivers/tty/serial/Kconfig | 122 ++++++++++++++++++++-------------------- 4 files changed, 100 insertions(+), 101 deletions(-)
drivers/tty/Kconfig +22 -23
@@ -81,21 +81,21 @@ config HW_CONSOLE default y config VT_HW_CONSOLE_BINDING - bool "Support for binding and unbinding console drivers" - depends on HW_CONSOLE - default n - ---help--- - The virtual terminal is the device that interacts with the physical - terminal through console drivers. On these systems, at least one - console driver is loaded. In other configurations, additional console - drivers may be enabled, such as the framebuffer console. If more than - 1 console driver is enabled, setting this to 'y' will allow you to - select the console driver that will serve as the backend for the - virtual terminals. - - See <file:Documentation/console/console.txt> for more - information. For framebuffer console users, please refer to - <file:Documentation/fb/fbcon.txt>. + bool "Support for binding and unbinding console drivers" + depends on HW_CONSOLE + default n + ---help--- + The virtual terminal is the device that interacts with the physical + terminal through console drivers. On these systems, at least one + console driver is loaded. In other configurations, additional console + drivers may be enabled, such as the framebuffer console. If more than + 1 console driver is enabled, setting this to 'y' will allow you to + select the console driver that will serve as the backend for the + virtual terminals. + + See <file:Documentation/console/console.txt> for more + information. For framebuffer console users, please refer to + <file:Documentation/fb/fbcon.txt>. config UNIX98_PTYS bool "Unix98 PTY support" if EXPERT
@@ -137,7 +137,6 @@ config LEGACY_PTYS security. This option enables these legacy devices; on most systems, it is safe to say N. - config LEGACY_PTY_COUNT int "Maximum number of legacy PTY in use" depends on LEGACY_PTYS
@@ -172,16 +171,16 @@ config ROCKETPORT tristate "Comtrol RocketPort support" depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI) help - This driver supports Comtrol RocketPort and RocketModem PCI boards. - These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or - modems. For information about the RocketPort/RocketModem boards - and this driver read <file:Documentation/serial/rocket.txt>. + This driver supports Comtrol RocketPort and RocketModem PCI boards. + These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or + modems. For information about the RocketPort/RocketModem boards + and this driver read <file:Documentation/serial/rocket.txt>. To compile this driver as a module, choose M here: the module will be called rocket. If you want to compile this driver into the kernel, say Y here. If - you don't have a Comtrol RocketPort/RocketModem card installed, say N. + you don't have a Comtrol RocketPort/RocketModem card installed, say N. config CYCLADES tristate "Cyclades async mux support"
@@ -425,8 +424,8 @@ config MIPS_EJTAG_FDC_KGDB depends on MIPS_EJTAG_FDC_TTY && KGDB default y help - This enables the use of KGDB over an FDC channel, allowing KGDB to be - used remotely or when a serial port isn't available. + This enables the use of KGDB over an FDC channel, allowing KGDB to be + used remotely or when a serial port isn't available. config MIPS_EJTAG_FDC_KGDB_CHAN int "KGDB FDC channel"
drivers/tty/hvc/Kconfig +15 -15
@@ -70,23 +70,23 @@ config HVC_XEN_FRONTEND Xen driver for secondary virtual consoles config HVC_UDBG - bool "udbg based fake hypervisor console" - depends on PPC - select HVC_DRIVER - default n - help - This is meant to be used during HW bring up or debugging when - no other console mechanism exist but udbg, to get you a quick - console for userspace. Do NOT enable in production kernels. + bool "udbg based fake hypervisor console" + depends on PPC + select HVC_DRIVER + default n + help + This is meant to be used during HW bring up or debugging when + no other console mechanism exist but udbg, to get you a quick + console for userspace. Do NOT enable in production kernels. config HVC_DCC - bool "ARM JTAG DCC console" - depends on ARM || ARM64 - select HVC_DRIVER - help - This console uses the JTAG DCC on ARM to create a console under the HVC - driver. This console is used through a JTAG only on ARM. If you don't have - a JTAG then you probably don't want this option. + bool "ARM JTAG DCC console" + depends on ARM || ARM64 + select HVC_DRIVER + help + This console uses the JTAG DCC on ARM to create a console under the HVC + driver. This console is used through a JTAG only on ARM. If you don't have + a JTAG then you probably don't want this option. config HVC_RISCV_SBI bool "RISC-V SBI console support"
drivers/tty/serial/8250/Kconfig +2 -2
@@ -45,7 +45,7 @@ config SERIAL_8250_DEPRECATED_OPTIONS keep the 8250_core.* options around until they revert the changes they already did. - If 8250 is built as a module, this adds 8250_core alias instead. + If 8250 is built as a module, this adds 8250_core alias instead. If you did not notice yet and/or you have userspace from pre-3.7, it is safe (and recommended) to say N here.
@@ -329,7 +329,7 @@ config SERIAL_8250_BCM2835AUX Features and limitations of the UART are Registers are similar to 16650 registers, - set bits in the control registers that are unsupported + set bits in the control registers that are unsupported are ignored and read back as 0 7/8 bit operation with 1 start and 1 stop bit 8 symbols deep fifo for rx and tx
drivers/tty/serial/Kconfig +61 -61
202 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH 43/114 drivers: staging: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/staging/android/ion/Kconfig | 2 +- drivers/staging/emxx_udc/Kconfig | 10 ++++----- drivers/staging/fbtft/Kconfig | 12 +++++----- drivers/staging/fwserial/Kconfig | 26 +++++++++++----------- drivers/staging/greybus/Kconfig | 4 ++-- drivers/staging/media/tegra-vde/Kconfig | 4 ++-- drivers/staging/most/Kconfig | 10 ++++----- drivers/staging/nvec/Kconfig | 19 +++++++--------- drivers/staging/pi433/Kconfig | 24 ++++++++++---------- drivers/staging/speakup/Kconfig | 8 +++---- .../staging/vc04_services/bcm2835-audio/Kconfig | 13 +++++------ drivers/staging/vt6655/Kconfig | 9 ++++---- 12 files changed, 67 insertions(+), 74 deletions(-)
drivers/staging/android/ion/Kconfig +1 -1
@@ -30,7 +30,7 @@ config ION_CHUNK_HEAP bool "Ion chunk heap support" depends on ION help - Choose this option to enable chunk heaps with Ion. This heap is + Choose this option to enable chunk heaps with Ion. This heap is similar in function the carveout heap but memory is broken down into smaller chunk sizes, typically corresponding to a TLB size. Unless you know your system has these regions, you should say N here.
drivers/staging/emxx_udc/Kconfig +5 -5
@@ -2,9 +2,9 @@ config USB_EMXX tristate "EMXX USB Function Device Controller" depends on USB_GADGET && (ARCH_RENESAS || (ARM && COMPILE_TEST)) help - The Emma Mobile series of SoCs from Renesas Electronics and - former NEC Electronics include USB Function hardware. + The Emma Mobile series of SoCs from Renesas Electronics and + former NEC Electronics include USB Function hardware. - Say "y" to link the driver statically, or "m" to build a - dynamically linked module called "emxx_udc" and force all - gadget drivers to also be dynamically linked. + Say "y" to link the driver statically, or "m" to build a + dynamically linked module called "emxx_udc" and force all + gadget drivers to also be dynamically linked.
drivers/staging/fbtft/Kconfig +6 -6
@@ -94,8 +94,8 @@ config FB_TFT_PCD8544 Generic Framebuffer support for PCD8544 config FB_TFT_RA8875 - tristate "FB driver for the RA8875 LCD Controller" - depends on FB_TFT + tristate "FB driver for the RA8875 LCD Controller" + depends on FB_TFT help Generic Framebuffer support for RA8875
@@ -124,10 +124,10 @@ config FB_TFT_SSD1289 Framebuffer support for SSD1289 config FB_TFT_SSD1305 - tristate "FB driver for the SSD1305 OLED Controller" - depends on FB_TFT - help - Framebuffer support for SSD1305 + tristate "FB driver for the SSD1305 OLED Controller" + depends on FB_TFT + help + Framebuffer support for SSD1305 config FB_TFT_SSD1306 tristate "FB driver for the SSD1306 OLED Controller"
drivers/staging/fwserial/Kconfig +13 -13
@@ -1,8 +1,8 @@ config FIREWIRE_SERIAL - tristate "TTY over Firewire" - depends on FIREWIRE && TTY - help - This enables TTY over IEEE 1394, providing high-speed serial + tristate "TTY over Firewire" + depends on FIREWIRE && TTY + help + This enables TTY over IEEE 1394, providing high-speed serial connectivity to cabled peers. This driver implements a ad-hoc transport protocol and is currently limited to Linux-to-Linux communication.
@@ -13,18 +13,18 @@ config FIREWIRE_SERIAL if FIREWIRE_SERIAL config FWTTY_MAX_TOTAL_PORTS - int "Maximum number of serial ports supported" - default "64" - help - Set this to the maximum number of serial ports you want the + int "Maximum number of serial ports supported" + default "64" + help + Set this to the maximum number of serial ports you want the firewire-serial driver to support. config FWTTY_MAX_CARD_PORTS - int "Maximum number of serial ports supported per adapter" - range 0 FWTTY_MAX_TOTAL_PORTS - default "32" - help - Set this to the maximum number of serial ports each firewire + int "Maximum number of serial ports supported per adapter" + range 0 FWTTY_MAX_TOTAL_PORTS + default "32" + help + Set this to the maximum number of serial ports each firewire adapter supports. The actual number of serial ports registered is set with the module parameter "ttys".
drivers/staging/greybus/Kconfig +2 -2
@@ -216,7 +216,7 @@ config GREYBUS_USB To compile this code as a module, chose M here: the module will be called gb-usb.ko -endif # GREYBUS_BRIDGED_PHY +endif # GREYBUS_BRIDGED_PHY config GREYBUS_ARCHE tristate "Greybus Arche Platform driver"
@@ -227,4 +227,4 @@ config GREYBUS_ARCHE To compile this code as a module, chose M here: the module will be called gb-arche.ko -endif # GREYBUS +endif # GREYBUS
drivers/staging/media/tegra-vde/Kconfig +2 -2
@@ -4,5 +4,5 @@ config TEGRA_VDE select DMA_SHARED_BUFFER select SRAM help - Say Y here to enable support for the NVIDIA Tegra video decoder - driver. + Say Y here to enable support for the NVIDIA Tegra video decoder + driver.
drivers/staging/most/Kconfig +4 -6
@@ -1,8 +1,8 @@ menuconfig MOST - tristate "MOST support" + tristate "MOST support" depends on HAS_DMA - default n - ---help--- + default n + ---help--- Say Y here if you want to enable MOST support. This driver needs at least one additional component to enable the desired access from userspace (e.g. character devices) and one that
@@ -11,9 +11,7 @@ menuconfig MOST To compile this driver as a module, choose M here: the module will be called most_core. - If in doubt, say N here. - - + If in doubt, say N here. if MOST
drivers/staging/nvec/Kconfig +8 -11
@@ -3,11 +3,11 @@ config MFD_NVEC depends on I2C && GPIOLIB && ARCH_TEGRA select MFD_CORE help - Say Y here to enable support for a nVidia compliant embedded - controller. + Say Y here to enable support for a nVidia compliant embedded + controller. - To compile this driver as a module, say M here: the module will be - called mfd-nvec + To compile this driver as a module, say M here: the module will be + called mfd-nvec config KEYBOARD_NVEC tristate "Keyboard on nVidia compliant EC"
@@ -17,7 +17,7 @@ config KEYBOARD_NVEC a nVidia compliant embedded controller. To compile this driver as a module, say M here: the module will be - called keyboard-nvec + called keyboard-nvec config SERIO_NVEC_PS2 tristate "PS2 on nVidia EC"
@@ -27,8 +27,7 @@ config SERIO_NVEC_PS2 to a nVidia compliant embedded controller. To compile this driver as a module, say M here: the module will be - called serio-nvec-ps2 - + called serio-nvec-ps2 config NVEC_POWER tristate "NVEC charger and battery"
@@ -38,8 +37,7 @@ config NVEC_POWER nVidia compliant embedded controllers. To compile this driver as a module, say M here: the module will be - called nvec-power - + called nvec-power config NVEC_PAZ00 tristate "Support for OEM specific functions on Compal PAZ00 based devices"
@@ -49,5 +47,4 @@ config NVEC_PAZ00 devices, e.g. Toshbia AC100 and Dynabooks AZ netbooks. To compile this driver as a module, say M here: the module will be - called nvec-paz00 - + called nvec-paz00
drivers/staging/pi433/Kconfig +12 -12
@@ -1,16 +1,16 @@ config PI433 - tristate "Pi433 - a 433MHz radio module for Raspberry Pi" - depends on SPI - help - This option allows you to enable support for the radio module Pi433. + tristate "Pi433 - a 433MHz radio module for Raspberry Pi" + depends on SPI + help + This option allows you to enable support for the radio module Pi433. - Pi433 is a shield that fits onto the GPIO header of a Raspberry Pi - or compatible. It extends the Raspberry Pi with the option, to - send and receive data in the 433MHz ISM band - for example to - communicate between two systems without using ethernet or bluetooth - or for control or read sockets, actors, sensors, widely available - for low price. + Pi433 is a shield that fits onto the GPIO header of a Raspberry Pi + or compatible. It extends the Raspberry Pi with the option, to + send and receive data in the 433MHz ISM band - for example to + communicate between two systems without using ethernet or bluetooth + or for control or read sockets, actors, sensors, widely available + for low price. - For details or the option to buy, please visit https://pi433.de/en.html + For details or the option to buy, please visit https://pi433.de/en.html - If in doubt, say N here, but saying yes most probably won't hurt + If in doubt, say N here, but saying yes most probably won't hurt
drivers/staging/speakup/Kconfig +4 -4
@@ -31,7 +31,6 @@ config SPEAKUP used in conjunction with Speakup. Think of them as video cards for blind people. - The Dectalk pc driver can only be built as a module, and requires software to be pre-loaded on to the card before the module can be loaded. See the decpc choice below
@@ -70,7 +69,7 @@ config SPEAKUP_SYNTH_AUDPTR tristate "Audapter synthesizer support" help This is the Speakup driver for the Audapter synthesizer. - You can say y to build it into the kernel, or m to + You can say y to build it into the kernel, or m to build it as a module. See the configuration help on the Speakup choice above for more info.
@@ -172,7 +171,7 @@ config SPEAKUP_SYNTH_SPKOUT help This is the Speakup driver for the Speakout synthesizer. - You can say y to build it into the kernel, or m to + You can say y to build it into the kernel, or m to build it as a module. See the configuration help on the Speakup choice above for more info.
@@ -195,5 +194,6 @@ config SPEAKUP_SYNTH_DUMMY the kernel, or m to build it as a module. See the configuration help on the Speakup choice above for more info. -endif # SPEAKUP +endif # SPEAKUP + endmenu
drivers/staging/vc04_services/bcm2835-audio/Kconfig +6 -7
@@ -1,8 +1,7 @@ config SND_BCM2835 - tristate "BCM2835 Audio" - depends on (ARCH_BCM2835 || COMPILE_TEST) && SND - select SND_PCM - select BCM2835_VCHIQ - help - Say Y or M if you want to support BCM2835 built in audio - + tristate "BCM2835 Audio" + depends on (ARCH_BCM2835 || COMPILE_TEST) && SND + select SND_PCM + select BCM2835_VCHIQ + help + Say Y or M if you want to support BCM2835 built in audio
drivers/staging/vt6655/Kconfig +4 -5
@@ -1,6 +1,5 @@ config VT6655 - tristate "VIA Technologies VT6655 support" - depends on PCI && MAC80211 && m - ---help--- - This is a vendor-written driver for VIA VT6655. - + tristate "VIA Technologies VT6655 support" + depends on PCI && MAC80211 && m + ---help--- + This is a vendor-written driver for VIA VT6655.
Signature · 1 line
1.9.1
PATCH 44/114 kernel: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- kernel/irq/Kconfig | 26 +++---- kernel/power/Kconfig | 12 +-- kernel/rcu/Kconfig | 2 +- kernel/time/Kconfig | 20 ++--- kernel/trace/Kconfig | 205 +++++++++++++++++++++++++-------------------------- 5 files changed, 132 insertions(+), 133 deletions(-)
kernel/irq/Kconfig +13 -13
@@ -3,11 +3,11 @@ menu "IRQ subsystem" # Make sparse irq Kconfig switch below available config MAY_HAVE_SPARSE_IRQ - bool + bool # Legacy support, required for itanic config GENERIC_IRQ_LEGACY - bool + bool # Enable the generic irq autoprobe mechanism config GENERIC_IRQ_PROBE
@@ -15,20 +15,20 @@ config GENERIC_IRQ_PROBE # Use the generic /proc/interrupts implementation config GENERIC_IRQ_SHOW - bool + bool # Print level/edge extra information config GENERIC_IRQ_SHOW_LEVEL - bool + bool # Supports effective affinity mask config GENERIC_IRQ_EFFECTIVE_AFF_MASK - bool + bool # Facility to allocate a hardware interrupt. This is legacy support # and should not be used in new code. Use irq domains instead. config GENERIC_IRQ_LEGACY_ALLOC_HWIRQ - bool + bool # Support for delayed migration from interrupt context config GENERIC_PENDING_IRQ
@@ -40,24 +40,24 @@ config GENERIC_IRQ_MIGRATION # Alpha specific irq affinity mechanism config AUTO_IRQ_AFFINITY - bool + bool # Tasklet based software resend for pending interrupts on enable_irq() config HARDIRQS_SW_RESEND - bool + bool # Preflow handler support for fasteoi (sparc64) config IRQ_PREFLOW_FASTEOI - bool + bool # Edge style eoi based handler (cell) config IRQ_EDGE_EOI_HANDLER - bool + bool # Generic configurable interrupt chip implementation config GENERIC_IRQ_CHIP - bool - select IRQ_DOMAIN + bool + select IRQ_DOMAIN # Generic irq_domain hw <--> linux irq number translation config IRQ_DOMAIN
@@ -105,7 +105,7 @@ config GENERIC_IRQ_RESERVATION_MODE # Support forced irq threading config IRQ_FORCED_THREADING - bool + bool config SPARSE_IRQ bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ
kernel/power/Kconfig +6 -6
@@ -85,20 +85,20 @@ config PM_STD_PARTITION default "" ---help--- The default resume partition is the partition that the suspend- - to-disk implementation will look for a suspended disk image. + to-disk implementation will look for a suspended disk image. - The partition specified here will be different for almost every user. + The partition specified here will be different for almost every user. It should be a valid swap partition (at least for now) that is turned - on before suspending. + on before suspending. The partition specified can be overridden by specifying: - resume=/dev/<other device> + resume=/dev/<other device> - which will set the resume partition to the device specified. + which will set the resume partition to the device specified. Note there is currently not a way to specify which device to save the - suspended image to. It will simply pick the first available swap + suspended image to. It will simply pick the first available swap device. config PM_SLEEP
kernel/rcu/Kconfig +1 -1
@@ -154,7 +154,7 @@ config RCU_FAST_NO_HZ for example, slowing down synchronize_rcu(). Say Y if energy efficiency is critically important, and you - don't care about increased grace-period durations. + don't care about increased grace-period durations. Say N if you are unsure.
kernel/time/Kconfig +10 -10
@@ -101,19 +101,19 @@ config NO_HZ_FULL select IRQ_WORK select CPU_ISOLATION help - Adaptively try to shutdown the tick whenever possible, even when - the CPU is running tasks. Typically this requires running a single - task on the CPU. Chances for running tickless are maximized when - the task mostly runs in userspace and has few kernel activity. + Adaptively try to shutdown the tick whenever possible, even when + the CPU is running tasks. Typically this requires running a single + task on the CPU. Chances for running tickless are maximized when + the task mostly runs in userspace and has few kernel activity. - You need to fill up the nohz_full boot parameter with the - desired range of dynticks CPUs. + You need to fill up the nohz_full boot parameter with the + desired range of dynticks CPUs. - This is implemented at the expense of some overhead in user <-> kernel - transitions: syscalls, exceptions and interrupts. Even when it's - dynamically off. + This is implemented at the expense of some overhead in user <-> kernel + transitions: syscalls, exceptions and interrupts. Even when it's + dynamically off. - Say N. + Say N. endchoice
kernel/trace/Kconfig +102 -103
292 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH 45/114 drivers: char: tpm: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/char/tpm/Kconfig | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-)
drivers/char/tpm/Kconfig +12 -11
@@ -12,11 +12,11 @@ menuconfig TCG_TPM If you have a TPM security chip in your system, which implements the Trusted Computing Group's specification, say Yes and it will be accessible from within Linux. For - more information see <http://www.trustedcomputinggroup.org>. - An implementation of the Trusted Software Stack (TSS), the - userspace enablement piece of the specification, can be - obtained at: <http://sourceforge.net/projects/trousers>. To - compile this driver as a module, choose M here; the module + more information see <http://www.trustedcomputinggroup.org>. + An implementation of the Trusted Software Stack (TSS), the + userspace enablement piece of the specification, can be + obtained at: <http://sourceforge.net/projects/trousers>. To + compile this driver as a module, choose M here; the module will be called tpm. If unsure, say N. Notes: 1) For more TPM drivers enable CONFIG_PNP, CONFIG_ACPI
@@ -100,17 +100,17 @@ config TCG_NSC tristate "National Semiconductor TPM Interface" depends on X86 ---help--- - If you have a TPM security chip from National Semiconductor - say Yes and it will be accessible from within Linux. To - compile this driver as a module, choose M here; the module + If you have a TPM security chip from National Semiconductor + say Yes and it will be accessible from within Linux. To + compile this driver as a module, choose M here; the module will be called tpm_nsc. config TCG_ATMEL tristate "Atmel TPM Interface" depends on PPC64 || HAS_IOPORT_MAP ---help--- - If you have a TPM security chip from Atmel say Yes and it - will be accessible from within Linux. To compile this driver + If you have a TPM security chip from Atmel say Yes and it + will be accessible from within Linux. To compile this driver as a module, choose M here; the module will be called tpm_atmel. config TCG_INFINEON
@@ -123,7 +123,8 @@ config TCG_INFINEON To compile this driver as a module, choose M here; the module will be called tpm_infineon. Further information on this driver and the supported hardware - can be found at http://www.trust.rub.de/projects/linux-device-driver-infineon-tpm/ + can be found at: + <http://www.trust.rub.de/projects/linux-device-driver-infineon-tpm/> config TCG_IBMVTPM tristate "IBM VTPM Interface"
Signature · 1 line
1.9.1
PATCH 46/114 lib: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- lib/Kconfig | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
lib/Kconfig +8 -8
@@ -506,7 +506,7 @@ config NLATTR # Generic 64-bit atomic support is selected if needed # config GENERIC_ATOMIC64 - bool + bool config LRU_CACHE tristate
@@ -563,23 +563,23 @@ config OID_REGISTRY Enable fast lookup object identifier registry. config UCS2_STRING - tristate + tristate source "lib/fonts/Kconfig" config SG_SPLIT def_bool n help - Provides a helper to split scatterlists into chunks, each chunk being - a scatterlist. This should be selected by a driver or an API which - whishes to split a scatterlist amongst multiple DMA channels. + Provides a helper to split scatterlists into chunks, each chunk being + a scatterlist. This should be selected by a driver or an API which + whishes to split a scatterlist amongst multiple DMA channels. config SG_POOL def_bool n help - Provides a helper to allocate chained scatterlists. This should be - selected by a driver or an API which whishes to allocate chained - scatterlist. + Provides a helper to allocate chained scatterlists. This should be + selected by a driver or an API which whishes to allocate chained + scatterlist. # # sg chaining option
Signature · 1 line
1.9.1
PATCH 47/114 net: caif: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- net/caif/Kconfig | 48 ++++++++++++++++++++++++------------------------ 1 file changed, 24 insertions(+), 24 deletions(-)
net/caif/Kconfig +24 -24
@@ -7,47 +7,47 @@ menuconfig CAIF select CRC_CCITT default n ---help--- - The "Communication CPU to Application CPU Interface" (CAIF) is a packet - based connection-oriented MUX protocol developed by ST-Ericsson for use - with its modems. It is accessed from user space as sockets (PF_CAIF). + The "Communication CPU to Application CPU Interface" (CAIF) is a packet + based connection-oriented MUX protocol developed by ST-Ericsson for use + with its modems. It is accessed from user space as sockets (PF_CAIF). - Say Y (or M) here if you build for a phone product (e.g. Android or - MeeGo ) that uses CAIF as transport, if unsure say N. + Say Y (or M) here if you build for a phone product (e.g. Android or + MeeGo ) that uses CAIF as transport, if unsure say N. - If you select to build it as module then CAIF_NETDEV also needs to be - built as modules. You will also need to say yes to any CAIF physical - devices that your platform requires. + If you select to build it as module then CAIF_NETDEV also needs to be + built as modules. You will also need to say yes to any CAIF physical + devices that your platform requires. - See Documentation/networking/caif for a further explanation on how to - use and configure CAIF. + See Documentation/networking/caif for a further explanation on how to + use and configure CAIF. -config CAIF_DEBUG +config CAIF_DEBUG bool "Enable Debug" depends on CAIF default n ---help--- - Enable the inclusion of debug code in the CAIF stack. - Be aware that doing this will impact performance. - If unsure say N. + Enable the inclusion of debug code in the CAIF stack. + Be aware that doing this will impact performance. + If unsure say N. config CAIF_NETDEV tristate "CAIF GPRS Network device" depends on CAIF default CAIF ---help--- - Say Y if you will be using a CAIF based GPRS network device. - This can be either built-in or a loadable module, - If you select to build it as a built-in then the main CAIF device must - also be a built-in. - If unsure say Y. + Say Y if you will be using a CAIF based GPRS network device. + This can be either built-in or a loadable module, + If you select to build it as a built-in then the main CAIF device must + also be a built-in. + If unsure say Y. config CAIF_USB tristate "CAIF USB support" depends on CAIF default n ---help--- - Say Y if you are using CAIF over USB CDC NCM. - This can be either built-in or a loadable module, - If you select to build it as a built-in then the main CAIF device must - also be a built-in. - If unsure say N. + Say Y if you are using CAIF over USB CDC NCM. + This can be either built-in or a loadable module, + If you select to build it as a built-in then the main CAIF device must + also be a built-in. + If unsure say N.
Signature · 1 line
1.9.1
PATCH 48/114 samples: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- samples/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
samples/Kconfig +3 -3
@@ -13,11 +13,11 @@ config SAMPLE_TRACE_EVENTS This build trace event example modules. config SAMPLE_TRACE_PRINTK - tristate "Build trace_printk module - tests various trace_printk formats" + tristate "Build trace_printk module - tests various trace_printk formats" depends on EVENT_TRACING && m help - This builds a module that calls trace_printk() and can be used to - test various trace_printk() calls from a module. + This builds a module that calls trace_printk() and can be used to + test various trace_printk() calls from a module. config SAMPLE_KOBJECT tristate "Build kobject examples -- loadable modules only"
Signature · 1 line
1.9.1
PATCH 49/114 security: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- security/apparmor/Kconfig | 22 +++++++++++----------- security/integrity/Kconfig | 32 ++++++++++++++++---------------- security/integrity/evm/Kconfig | 10 +++++----- 3 files changed, 32 insertions(+), 32 deletions(-)
security/apparmor/Kconfig +11 -11
@@ -25,17 +25,17 @@ config SECURITY_APPARMOR_HASH is available to userspace via the apparmor filesystem. config SECURITY_APPARMOR_HASH_DEFAULT - bool "Enable policy hash introspection by default" - depends on SECURITY_APPARMOR_HASH - default y - help - This option selects whether sha1 hashing of loaded policy - is enabled by default. The generation of sha1 hashes for - loaded policy provide system administrators a quick way - to verify that policy in the kernel matches what is expected, - however it can slow down policy load on some devices. In - these cases policy hashing can be disabled by default and - enabled only if needed. + bool "Enable policy hash introspection by default" + depends on SECURITY_APPARMOR_HASH + default y + help + This option selects whether sha1 hashing of loaded policy + is enabled by default. The generation of sha1 hashes for + loaded policy provide system administrators a quick way + to verify that policy in the kernel matches what is expected, + however it can slow down policy load on some devices. In + these cases policy hashing can be disabled by default and + enabled only if needed. config SECURITY_APPARMOR_DEBUG bool "Build AppArmor with debug code"
security/integrity/Kconfig +16 -16
@@ -33,10 +33,10 @@ config INTEGRITY_ASYMMETRIC_KEYS bool "Enable asymmetric keys support" depends on INTEGRITY_SIGNATURE default n - select ASYMMETRIC_KEY_TYPE - select ASYMMETRIC_PUBLIC_KEY_SUBTYPE - select CRYPTO_RSA - select X509_CERTIFICATE_PARSER + select ASYMMETRIC_KEY_TYPE + select ASYMMETRIC_PUBLIC_KEY_SUBTYPE + select CRYPTO_RSA + select X509_CERTIFICATE_PARSER help This option enables digital signature verification using asymmetric keys.
@@ -47,20 +47,20 @@ config INTEGRITY_TRUSTED_KEYRING depends on INTEGRITY_ASYMMETRIC_KEYS default y help - This option requires that all keys added to the .ima and - .evm keyrings be signed by a key on the system trusted - keyring. + This option requires that all keys added to the .ima and + .evm keyrings be signed by a key on the system trusted + keyring. config INTEGRITY_PLATFORM_KEYRING - bool "Provide keyring for platform/firmware trusted keys" - depends on INTEGRITY_ASYMMETRIC_KEYS - depends on SYSTEM_BLACKLIST_KEYRING - depends on EFI - help - Provide a separate, distinct keyring for platform trusted keys, which - the kernel automatically populates during initialization from values - provided by the platform for verifying the kexec'ed kerned image - and, possibly, the initramfs signature. + bool "Provide keyring for platform/firmware trusted keys" + depends on INTEGRITY_ASYMMETRIC_KEYS + depends on SYSTEM_BLACKLIST_KEYRING + depends on EFI + help + Provide a separate, distinct keyring for platform trusted keys, which + the kernel automatically populates during initialization from values + provided by the platform for verifying the kexec'ed kerned image + and, possibly, the initramfs signature. config INTEGRITY_AUDIT bool "Enables integrity auditing support "
security/integrity/evm/Kconfig +5 -5
@@ -59,15 +59,15 @@ config EVM_LOAD_X509 depends on EVM && INTEGRITY_TRUSTED_KEYRING default n help - Load an X509 certificate onto the '.evm' trusted keyring. + Load an X509 certificate onto the '.evm' trusted keyring. - This option enables X509 certificate loading from the kernel - onto the '.evm' trusted keyring. A public key can be used to - verify EVM integrity starting from the 'init' process. + This option enables X509 certificate loading from the kernel + onto the '.evm' trusted keyring. A public key can be used to + verify EVM integrity starting from the 'init' process. config EVM_X509_PATH string "EVM X509 certificate path" depends on EVM_LOAD_X509 default "/etc/keys/x509_evm.der" help - This option defines X509 certificate path. + This option defines X509 certificate path.
Signature · 1 line
1.9.1
PATCH 50/114 net: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- net/Kconfig | 14 +-- net/batman-adv/Kconfig | 10 +- net/bluetooth/Kconfig | 2 +- net/ife/Kconfig | 2 +- net/ipv4/Kconfig | 231 ++++++++++++++++++++++---------------------- net/ipv4/netfilter/Kconfig | 4 +- net/ipv6/netfilter/Kconfig | 26 ++--- net/mpls/Kconfig | 10 +- net/netfilter/Kconfig | 10 +- net/netfilter/ipset/Kconfig | 2 +- net/netfilter/ipvs/Kconfig | 68 ++++++------- net/nfc/hci/Kconfig | 14 +-- net/rds/Kconfig | 4 +- net/sched/Kconfig | 130 ++++++++++++------------- net/wireless/Kconfig | 38 ++++---- net/xfrm/Kconfig | 10 +- 16 files changed, 287 insertions(+), 288 deletions(-)
net/Kconfig +7 -7
@@ -259,7 +259,7 @@ config XPS default y config HWBM - bool + bool config CGROUP_NET_PRIO bool "Network priority cgroup"
@@ -310,12 +310,12 @@ config BPF_STREAM_PARSER select STREAM_PARSER select NET_SOCK_MSG ---help--- - Enabling this allows a stream parser to be used with - BPF_MAP_TYPE_SOCKMAP. + Enabling this allows a stream parser to be used with + BPF_MAP_TYPE_SOCKMAP. - BPF_MAP_TYPE_SOCKMAP provides a map type to use with network sockets. - It can be used to enforce socket policy, implement socket redirects, - etc. + BPF_MAP_TYPE_SOCKMAP provides a map type to use with network sockets. + It can be used to enforce socket policy, implement socket redirects, + etc. config NET_FLOW_LIMIT bool
@@ -436,7 +436,7 @@ config NET_DEVLINK monitoring. config PAGE_POOL - bool + bool config FAILOVER tristate "Generic failover module"
net/batman-adv/Kconfig +5 -5
@@ -24,11 +24,11 @@ config BATMAN_ADV depends on NET select LIBCRC32C help - B.A.T.M.A.N. (better approach to mobile ad-hoc networking) is - a routing protocol for multi-hop ad-hoc mesh networks. The - networks may be wired or wireless. See - https://www.open-mesh.org/ for more information and user space - tools. + B.A.T.M.A.N. (better approach to mobile ad-hoc networking) is + a routing protocol for multi-hop ad-hoc mesh networks. The + networks may be wired or wireless. See + https://www.open-mesh.org/ for more information and user space + tools. config BATMAN_ADV_BATMAN_V bool "B.A.T.M.A.N. V protocol"
net/bluetooth/Kconfig +1 -1
@@ -28,7 +28,7 @@ menuconfig BT L2CAP (Logical Link Control and Adaptation Protocol) SMP (Security Manager Protocol) on LE (Low Energy) links HCI Device drivers (Interface to the hardware) - RFCOMM Module (RFCOMM Protocol) + RFCOMM Module (RFCOMM Protocol) BNEP Module (Bluetooth Network Encapsulation Protocol) CMTP Module (CAPI Message Transport Protocol) HIDP Module (Human Interface Device Protocol)
net/ife/Kconfig +1 -1
@@ -4,7 +4,7 @@ menuconfig NET_IFE depends on NET - tristate "Inter-FE based on IETF ForCES InterFE LFB" + tristate "Inter-FE based on IETF ForCES InterFE LFB" default n help Say Y here to add support of IFE encapsulation protocol
net/ipv4/Kconfig +115 -116
323 lines not on this page · raw message
net/ipv4/netfilter/Kconfig +2 -2
@@ -294,7 +294,7 @@ config IP_NF_TARGET_ECN depends on NETFILTER_ADVANCED ---help--- This option adds a `ECN' target, which can be used in the iptables mangle - table. + table. You can use this target to remove the ECN bits from the IPv4 header of an IP packet. This is particularly useful, if you need to work around
@@ -331,7 +331,7 @@ config IP_NF_SECURITY help This option adds a `security' table to iptables, for use with Mandatory Access Control (MAC) policy. - + If unsure, say N. endif # IP_NF_IPTABLES
net/ipv6/netfilter/Kconfig +13 -13
@@ -177,13 +177,13 @@ config IP6_NF_MATCH_RT To compile it as a module, choose M here. If unsure, say N. config IP6_NF_MATCH_SRH - tristate '"srh" Segment Routing header match support' - depends on NETFILTER_ADVANCED - help - srh matching allows you to match packets based on the segment + tristate '"srh" Segment Routing header match support' + depends on NETFILTER_ADVANCED + help + srh matching allows you to match packets based on the segment routing header of the packet. - To compile it as a module, choose M here. If unsure, say N. + To compile it as a module, choose M here. If unsure, say N. # The targets config IP6_NF_TARGET_HL
@@ -252,14 +252,14 @@ config IP6_NF_RAW # security table for MAC policy config IP6_NF_SECURITY - tristate "Security table" - depends on SECURITY - depends on NETFILTER_ADVANCED - help - This option adds a `security' table to iptables, for use - with Mandatory Access Control (MAC) policy. - - If unsure, say N. + tristate "Security table" + depends on SECURITY + depends on NETFILTER_ADVANCED + help + This option adds a `security' table to iptables, for use + with Mandatory Access Control (MAC) policy. + + If unsure, say N. config IP6_NF_NAT tristate "ip6tables NAT support"
net/mpls/Kconfig +5 -5
@@ -18,20 +18,20 @@ if MPLS config NET_MPLS_GSO tristate "MPLS: GSO support" help - This is helper module to allow segmentation of non-MPLS GSO packets - that have had MPLS stack entries pushed onto them and thus - become MPLS GSO packets. + This is helper module to allow segmentation of non-MPLS GSO packets + that have had MPLS stack entries pushed onto them and thus + become MPLS GSO packets. config MPLS_ROUTING tristate "MPLS: routing support" depends on NET_IP_TUNNEL || NET_IP_TUNNEL=n ---help--- - Add support for forwarding of mpls packets. + Add support for forwarding of mpls packets. config MPLS_IPTUNNEL tristate "MPLS: IP over MPLS tunnel support" depends on LWTUNNEL && MPLS_ROUTING ---help--- - mpls ip tunnel support. + mpls ip tunnel support. endif # MPLS
net/netfilter/Kconfig +5 -5
@@ -33,7 +33,7 @@ config NETFILTER_NETLINK_QUEUE help If this option is enabled, the kernel will include support for queueing packets via NFNETLINK. - + config NETFILTER_NETLINK_LOG tristate "Netfilter LOG over NFNETLINK interface" default m if NETFILTER_ADVANCED=n
@@ -692,7 +692,7 @@ config NF_FLOW_TABLE_INET tristate "Netfilter flow table mixed IPv4/IPv6 module" depends on NF_FLOW_TABLE help - This option adds the flow table mixed IPv4/IPv6 support. + This option adds the flow table mixed IPv4/IPv6 support. To compile it as a module, choose M here.
@@ -793,7 +793,7 @@ config NETFILTER_XT_TARGET_CLASSIFY the priority of a packet. Some qdiscs can use this value for classification, among these are: - atm, cbq, dsmark, pfifo_fast, htb, prio + atm, cbq, dsmark, pfifo_fast, htb, prio To compile it as a module, choose M here. If unsure, say N.
@@ -1482,7 +1482,7 @@ config NETFILTER_XT_MATCH_REALM This option adds a `realm' match, which allows you to use the realm key from the routing subsystem inside iptables. - This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option + This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option in tc world. If you want to compile it as a module, say M here and read
@@ -1503,7 +1503,7 @@ config NETFILTER_XT_MATCH_SCTP depends on NETFILTER_ADVANCED default IP_SCTP help - With this option enabled, you will be able to use the + With this option enabled, you will be able to use the `sctp' match in order to match on SCTP source/destination ports and SCTP chunk types.
net/netfilter/ipset/Kconfig +1 -1
@@ -18,7 +18,7 @@ config IP_SET_MAX range 2 65534 depends on IP_SET help - You can define here default value of the maximum number + You can define here default value of the maximum number of IP sets for the kernel. The value can be overridden by the 'max_sets' module
net/netfilter/ipvs/Kconfig +34 -34
218 lines not on this page · raw message
net/nfc/hci/Kconfig +7 -7
@@ -1,11 +1,11 @@ config NFC_HCI - depends on NFC - tristate "NFC HCI implementation" - default n - help - Say Y here if you want to build support for a kernel NFC HCI - implementation. This is mostly needed for devices that only process - HCI frames, like for example the NXP pn544. + depends on NFC + tristate "NFC HCI implementation" + default n + help + Say Y here if you want to build support for a kernel NFC HCI + implementation. This is mostly needed for devices that only process + HCI frames, like for example the NXP pn544. config NFC_SHDLC depends on NFC_HCI
net/rds/Kconfig +2 -2
@@ -22,6 +22,6 @@ config RDS_TCP This transport does not support RDMA operations. config RDS_DEBUG - bool "RDS debugging messages" + bool "RDS debugging messages" depends on RDS - default n + default n
net/sched/Kconfig +65 -65
239 lines not on this page · raw message
net/wireless/Kconfig +19 -19
@@ -137,25 +137,25 @@ config CFG80211_REG_RELAX_NO_IR bool "cfg80211 support for NO_IR relaxation" depends on CFG80211_CERTIFICATION_ONUS ---help--- - This option enables support for relaxation of the NO_IR flag for - situations that certain regulatory bodies have provided clarifications - on how relaxation can occur. This feature has an inherent dependency on - userspace features which must have been properly tested and as such is - not enabled by default. - - A relaxation feature example is allowing the operation of a P2P group - owner (GO) on channels marked with NO_IR if there is an additional BSS - interface which associated to an AP which userspace assumes or confirms - to be an authorized master, i.e., with radar detection support and DFS - capabilities. However, note that in order to not create daisy chain - scenarios, this relaxation is not allowed in cases where the BSS client - is associated to P2P GO and in addition the P2P GO instantiated on - a channel due to this relaxation should not allow connection from - non P2P clients. - - The regulatory core will apply these relaxations only for drivers that - support this feature by declaring the appropriate channel flags and - capabilities in their registration flow. + This option enables support for relaxation of the NO_IR flag for + situations that certain regulatory bodies have provided clarifications + on how relaxation can occur. This feature has an inherent dependency on + userspace features which must have been properly tested and as such is + not enabled by default. + + A relaxation feature example is allowing the operation of a P2P group + owner (GO) on channels marked with NO_IR if there is an additional BSS + interface which associated to an AP which userspace assumes or confirms + to be an authorized master, i.e., with radar detection support and DFS + capabilities. However, note that in order to not create daisy chain + scenarios, this relaxation is not allowed in cases where the BSS client + is associated to P2P GO and in addition the P2P GO instantiated on + a channel due to this relaxation should not allow connection from + non P2P clients. + + The regulatory core will apply these relaxations only for drivers that + support this feature by declaring the appropriate channel flags and + capabilities in their registration flow. config CFG80211_DEFAULT_PS bool "enable powersave by default"
net/xfrm/Kconfig +5 -5
@@ -2,13 +2,13 @@ # XFRM configuration # config XFRM - bool - depends on NET - select GRO_CELLS - select SKB_EXTENSIONS + bool + depends on NET + select GRO_CELLS + select SKB_EXTENSIONS config XFRM_OFFLOAD - bool + bool config XFRM_ALGO tristate
Signature · 1 line
1.9.1
Re: [PATCH 050/114] net: Kconfig: pedantic formatting
Quoted 27 lines · metux IT consult
Formatting of
Kconfigfiles doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.Signed-off-by Enrico Weigelt, metux IT consult <[email protected]>--- net/Kconfig | 14 +-- net/batman-adv/Kconfig | 10 +- net/bluetooth/Kconfig | 2 +- net/ife/Kconfig | 2 +- net/ipv4/Kconfig | 231 ++++++++++++++++++++++---------------------- net/ipv4/netfilter/Kconfig | 4 +- net/ipv6/netfilter/Kconfig | 26 ++--- net/mpls/Kconfig | 10 +- net/netfilter/Kconfig | 10 +- net/netfilter/ipset/Kconfig | 2 +- net/netfilter/ipvs/Kconfig | 68 ++++++------- net/nfc/hci/Kconfig | 14 +-- net/rds/Kconfig | 4 +- net/sched/Kconfig | 130 ++++++++++++------------- net/wireless/Kconfig | 38 ++++---- net/xfrm/Kconfig | 10 +- 16 files changed, 287 insertions(+), 288 deletions(-)config
TCP_CONG_NV
net/ipv4/Kconfig config TCP_CONG_BIC · line 563
Quoted 10 lines
net/ipv4/Kconfig +3
-7- tristate "TCP NV" - default n - ---help--- - TCP NV is a follow up to TCP Vegas. It has been modified to deal with - 10G networks, measurement noise introduced by LRO, GRO and interrupt - coalescence. In addition, it will decrease its cwnd multiplicatively - instead of linearly. + tristate "TCP NV" + default n + ---help---
You are touching this line,
so i want you to replace it to 'help' to fix checkpatch.pl warning.
WARNING: prefer 'help' over '---help---' for new help texts #560: FILE: net/ipv4/Kconfig:560:
+config TCP_CONG_NV
Quoted 17 lines
net/ipv4/Kconfig +9
-5+ TCP NV is a follow up to TCP Vegas. It has been modified to deal with + 10G networks, measurement noise introduced by LRO, GRO and interrupt + coalescence. In addition, it will decrease its cwnd multiplicatively + instead of linearly. - Note that in general congestion avoidance (cwnd decreased when # packets - queued grows) cannot coexist with congestion control (cwnd decreased only - when there is packet loss) due to fairness issues. One scenario when they - can coexist safely is when the CA flows have RTTs << CC flows RTTs. + Note that in general congestion avoidance (cwnd decreased when # packets + queued grows) cannot coexist with congestion control (cwnd decreased only + when there is packet loss) due to fairness issues. One scenario when they + can coexist safely is when the CA flows have RTTs << CC flows RTTs. - For further details see http://www.brakmo.org/networking/tcp-nv/ + For further details see http://www.brakmo.org/networking/tcp-nv/
Signature · 2 lines
Best Regards Masahiro Yamada
PATCH 51/114 fs: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- fs/9p/Kconfig | 2 -- fs/Kconfig | 6 +++--- fs/autofs/Kconfig | 36 ++++++++++++++++++------------------ fs/nfs/Kconfig | 6 +++--- fs/notify/fanotify/Kconfig | 22 +++++++++++----------- fs/orangefs/Kconfig | 4 ++-- fs/proc/Kconfig | 10 +++++----- fs/pstore/Kconfig | 18 +++++++++--------- fs/qnx6/Kconfig | 2 +- fs/quota/Kconfig | 2 +- fs/reiserfs/Kconfig | 4 ++-- fs/ubifs/Kconfig | 4 ++-- fs/ufs/Kconfig | 4 ++-- 13 files changed, 59 insertions(+), 61 deletions(-)
fs/9p/Kconfig +0 -2
@@ -17,7 +17,6 @@ config 9P_FSCACHE Choose Y here to enable persistent, read-only local caching support for 9p clients using FS-Cache - config 9P_FS_POSIX_ACL bool "9P POSIX Access Control Lists" select FS_POSIX_ACL
@@ -29,7 +28,6 @@ config 9P_FS_POSIX_ACL endif - config 9P_FS_SECURITY bool "9P Security Labels" depends on 9P_FS
fs/Kconfig +3 -3
@@ -6,7 +6,7 @@ menu "File systems" # Use unaligned word dcache accesses config DCACHE_WORD_ACCESS - bool + bool if BLOCK
@@ -90,8 +90,8 @@ config FILE_LOCKING default y help This option enables standard file locking support, required - for filesystems like NFS and for the flock() system - call. Disabling this option saves about 11k. + for filesystems like NFS and for the flock() system + call. Disabling this option saves about 11k. config MANDATORY_FILE_LOCKING bool "Enable Mandatory file locking"
fs/autofs/Kconfig +18 -18
@@ -2,30 +2,30 @@ config AUTOFS4_FS tristate "Old Kconfig name for Kernel automounter support" select AUTOFS_FS help - This name exists for people to just automatically pick up the - new name of the autofs Kconfig option. All it does is select - the new option name. + This name exists for people to just automatically pick up the + new name of the autofs Kconfig option. All it does is select + the new option name. - It will go away in a release or two as people have - transitioned to just plain AUTOFS_FS. + It will go away in a release or two as people have + transitioned to just plain AUTOFS_FS. config AUTOFS_FS tristate "Kernel automounter support (supports v3, v4 and v5)" default n help - The automounter is a tool to automatically mount remote file systems - on demand. This implementation is partially kernel-based to reduce - overhead in the already-mounted case; this is unlike the BSD - automounter (amd), which is a pure user space daemon. + The automounter is a tool to automatically mount remote file systems + on demand. This implementation is partially kernel-based to reduce + overhead in the already-mounted case; this is unlike the BSD + automounter (amd), which is a pure user space daemon. - To use the automounter you need the user-space tools from - <https://www.kernel.org/pub/linux/daemons/autofs/>; you also want - to answer Y to "NFS file system support", below. + To use the automounter you need the user-space tools from + <https://www.kernel.org/pub/linux/daemons/autofs/>; you also want + to answer Y to "NFS file system support", below. - To compile this support as a module, choose M here: the module will be - called autofs. + To compile this support as a module, choose M here: the module will be + called autofs. - If you are not a part of a fairly large, distributed network or - don't have a laptop which needs to dynamically reconfigure to the - local network, you probably do not need an automounter, and can say - N here. + If you are not a part of a fairly large, distributed network or + don't have a laptop which needs to dynamically reconfigure to the + local network, you probably do not need an automounter, and can say + N here.
fs/nfs/Kconfig +3 -3
@@ -147,10 +147,10 @@ config NFS_V4_1_MIGRATION default n help This option makes the NFS client advertise to NFSv4.1 servers that - it can support NFSv4 migration. + it can support NFSv4 migration. - The NFSv4.1 pieces of the Linux NFSv4 migration implementation are - still experimental. If you are not an NFSv4 developer, say N here. + The NFSv4.1 pieces of the Linux NFSv4 migration implementation are + still experimental. If you are not an NFSv4 developer, say N here. config NFS_V4_SECURITY_LABEL bool
fs/notify/fanotify/Kconfig +11 -11
@@ -5,12 +5,12 @@ config FANOTIFY select EXPORTFS default n ---help--- - Say Y here to enable fanotify support. fanotify is a file access - notification system which differs from inotify in that it sends - an open file descriptor to the userspace listener along with - the event. + Say Y here to enable fanotify support. fanotify is a file access + notification system which differs from inotify in that it sends + an open file descriptor to the userspace listener along with + the event. - If unsure, say Y. + If unsure, say Y. config FANOTIFY_ACCESS_PERMISSIONS bool "fanotify permissions checking"
@@ -18,10 +18,10 @@ config FANOTIFY_ACCESS_PERMISSIONS depends on SECURITY default n ---help--- - Say Y here is you want fanotify listeners to be able to make permissions - decisions concerning filesystem events. This is used by some fanotify - listeners which need to scan files before allowing the system access to - use those files. This is used by some anti-malware vendors and by some - hierarchical storage management systems. + Say Y here is you want fanotify listeners to be able to make permissions + decisions concerning filesystem events. This is used by some fanotify + listeners which need to scan files before allowing the system access to + use those files. This is used by some anti-malware vendors and by some + hierarchical storage management systems. - If unsure, say N. + If unsure, say N.
fs/orangefs/Kconfig +2 -2
@@ -2,5 +2,5 @@ config ORANGEFS_FS tristate "ORANGEFS (Powered by PVFS) support" select FS_POSIX_ACL help - Orange is a parallel file system designed for use on high end - computing (HEC) systems. + Orange is a parallel file system designed for use on high end + computing (HEC) systems.
fs/proc/Kconfig +5 -5
@@ -41,8 +41,8 @@ config PROC_VMCORE bool "/proc/vmcore support" depends on PROC_FS && CRASH_DUMP default y - help - Exports the dump image of crashed kernel in ELF format. + help + Exports the dump image of crashed kernel in ELF format. config PROC_VMCORE_DEVICE_DUMP bool "Device Hardware/Firmware Log Collection"
@@ -79,14 +79,14 @@ config PROC_SYSCTL limited in memory. config PROC_PAGE_MONITOR - default y + default y depends on PROC_FS && MMU bool "Enable /proc page monitoring" if EXPERT - help + help Various /proc files exist to monitor process memory utilization: /proc/pid/smaps, /proc/pid/clear_refs, /proc/pid/pagemap, /proc/kpagecount, and /proc/kpageflags. Disabling these - interfaces will reduce the size of the kernel by approximately 4kb. + interfaces will reduce the size of the kernel by approximately 4kb. config PROC_CHILDREN bool "Include /proc/<pid>/task/<tid>/children file"
fs/pstore/Kconfig +9 -9
@@ -3,15 +3,15 @@ config PSTORE select CRYPTO if PSTORE_COMPRESS default n help - This option enables generic access to platform level - persistent storage via "pstore" filesystem that can - be mounted as /dev/pstore. Only useful if you have - a platform level driver that registers with pstore to - provide the data, so you probably should just go say "Y" - (or "M") to a platform specific persistent store driver - (e.g. ACPI_APEI on X86) which will select this for you. - If you don't have a platform persistent store driver, - say N. + This option enables generic access to platform level + persistent storage via "pstore" filesystem that can + be mounted as /dev/pstore. Only useful if you have + a platform level driver that registers with pstore to + provide the data, so you probably should just go say "Y" + (or "M") to a platform specific persistent store driver + (e.g. ACPI_APEI on X86) which will select this for you. + If you don't have a platform persistent store driver, + say N. config PSTORE_DEFLATE_COMPRESS tristate "DEFLATE (ZLIB) compression"
fs/qnx6/Kconfig +1 -1
@@ -6,7 +6,7 @@ config QNX6FS_FS QNX 6 (also called QNX RTP). Further information is available at <http://www.qnx.com/>. Say Y if you intend to mount QNX hard disks or floppies formatted - with a mkqnx6fs. + with a mkqnx6fs. However, keep in mind that this currently is a readonly driver! To compile this file system support as a module, choose M here: the
fs/quota/Kconfig +1 -1
@@ -46,7 +46,7 @@ config QUOTA_DEBUG # Generic support for tree structured quota files. Selected when needed. config QUOTA_TREE - tristate + tristate config QFMT_V1 tristate "Old quota format support"
fs/reiserfs/Kconfig +2 -2
@@ -10,7 +10,7 @@ config REISERFS_FS In general, ReiserFS is as fast as ext2, but is very efficient with large directories and small files. Additional patches are needed - for NFS and quotas, please see + for NFS and quotas, please see <https://reiser4.wiki.kernel.org/index.php/Main_Page> for links. It is more easily extended to have features currently found in
@@ -19,7 +19,7 @@ config REISERFS_FS plugins consistent with our motto ``It takes more than a license to make source code open.'' - Read <https://reiser4.wiki.kernel.org/index.php/Main_Page> + Read <https://reiser4.wiki.kernel.org/index.php/Main_Page> to learn more about reiserfs. Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
fs/ubifs/Kconfig +2 -2
@@ -28,8 +28,8 @@ config UBIFS_FS_LZO bool "LZO compression support" if UBIFS_FS_ADVANCED_COMPR default y help - LZO compressor is generally faster than zlib but compresses worse. - Say 'Y' if unsure. + LZO compressor is generally faster than zlib but compresses worse. + Say 'Y' if unsure. config UBIFS_FS_ZLIB bool "ZLIB compression support" if UBIFS_FS_ADVANCED_COMPR
fs/ufs/Kconfig +2 -2
@@ -10,8 +10,8 @@ config UFS_FS experimental "UFS file system write support", below. Please read the file <file:Documentation/filesystems/ufs.txt> for more information. - The recently released UFS2 variant (used in FreeBSD 5.x) is - READ-ONLY supported. + The recently released UFS2 variant (used in FreeBSD 5.x) is + READ-ONLY supported. Note that this option is generally not needed for floppies, since a good portable way to transport files and directories between unixes
Signature · 1 line
1.9.1
PATCH 52/114 arch: x86: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- arch/x86/Kconfig | 140 +++++++++++++++++++++++++-------------------------- arch/x86/kvm/Kconfig | 4 +- arch/x86/xen/Kconfig | 8 +-- 3 files changed, 76 insertions(+), 76 deletions(-)
arch/x86/Kconfig +70 -70
@@ -432,8 +432,8 @@ config X86_MPPARSE (esp with 64bit cpus) with acpi support, MADT and DSDT will override it config GOLDFISH - def_bool y - depends on X86_GOLDFISH + def_bool y + depends on X86_GOLDFISH config RETPOLINE bool "Avoid speculative indirect branches in kernel"
@@ -554,12 +554,12 @@ config X86_UV # Please maintain the alphabetic order if and when there are additions config X86_GOLDFISH - bool "Goldfish (Virtual Platform)" - depends on X86_EXTENDED_PLATFORM - ---help--- - Enable support for the Goldfish virtual platform used primarily - for Android development. Unless you are building for the Android - Goldfish emulator say N here. + bool "Goldfish (Virtual Platform)" + depends on X86_EXTENDED_PLATFORM + ---help--- + Enable support for the Goldfish virtual platform used primarily + for Android development. Unless you are building for the Android + Goldfish emulator say N here. config X86_INTEL_CE bool "CE4100 TV platform"
@@ -870,16 +870,16 @@ config HPET_EMULATE_RTC depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y) config APB_TIMER - def_bool y if X86_INTEL_MID - prompt "Intel MID APB Timer Support" if X86_INTEL_MID - select DW_APB_TIMER - depends on X86_INTEL_MID && SFI - help - APB timer is the replacement for 8254, HPET on X86 MID platforms. - The APBT provides a stable time base on SMP - systems, unlike the TSC, but it is more expensive to access, - as it is off-chip. APB timers are always running regardless of CPU - C states, they are used as per CPU clockevent device when possible. + def_bool y if X86_INTEL_MID + prompt "Intel MID APB Timer Support" if X86_INTEL_MID + select DW_APB_TIMER + depends on X86_INTEL_MID && SFI + help + APB timer is the replacement for 8254, HPET on X86 MID platforms. + The APBT provides a stable time base on SMP + systems, unlike the TSC, but it is more expensive to access, + as it is off-chip. APB timers are always running regardless of CPU + C states, they are used as per CPU clockevent device when possible. # Mark as expert because too many people got it wrong. # The code disables itself when not needed.
@@ -1048,8 +1048,8 @@ config SCHED_MC_PRIO If unsure say Y here. config UP_LATE_INIT - def_bool y - depends on !SMP && X86_LOCAL_APIC + def_bool y + depends on !SMP && X86_LOCAL_APIC config X86_UP_APIC bool "Local APIC support on uniprocessors" if !PCI_MSI
@@ -1133,16 +1133,16 @@ config X86_MCE_INTEL prompt "Intel MCE features" depends on X86_MCE && X86_LOCAL_APIC ---help--- - Additional support for intel specific MCE features such as - the thermal monitor. + Additional support for intel specific MCE features such as + the thermal monitor. config X86_MCE_AMD def_bool y prompt "AMD MCE features" depends on X86_MCE && X86_LOCAL_APIC && AMD_NB ---help--- - Additional support for AMD specific MCE features such as - the DRAM Error Threshold. + Additional support for AMD specific MCE features such as + the DRAM Error Threshold. config X86_ANCIENT_MCE bool "Support for old Pentium 5 / WinChip machine checks"
@@ -1198,8 +1198,8 @@ config X86_LEGACY_VM86 If unsure, say N here. config VM86 - bool - default X86_LEGACY_VM86 + bool + default X86_LEGACY_VM86 config X86_16BIT bool "Enable support for 16-bit segments" if EXPERT
@@ -1220,22 +1220,22 @@ config X86_ESPFIX64 depends on X86_16BIT && X86_64 config X86_VSYSCALL_EMULATION - bool "Enable vsyscall emulation" if EXPERT - default y - depends on X86_64 - ---help--- - This enables emulation of the legacy vsyscall page. Disabling - it is roughly equivalent to booting with vsyscall=none, except - that it will also disable the helpful warning if a program - tries to use a vsyscall. With this option set to N, offending - programs will just segfault, citing addresses of the form - 0xffffffffff600?00. - - This option is required by many programs built before 2013, and - care should be used even with newer programs if set to N. - - Disabling this option saves about 7K of kernel size and - possibly 4K of additional runtime pagetable memory. + bool "Enable vsyscall emulation" if EXPERT + default y + depends on X86_64 + ---help--- + This enables emulation of the legacy vsyscall page. Disabling + it is roughly equivalent to booting with vsyscall=none, except + that it will also disable the helpful warning if a program + tries to use a vsyscall. With this option set to N, offending + programs will just segfault, citing addresses of the form + 0xffffffffff600?00. + + This option is required by many programs built before 2013, and + care should be used even with newer programs if set to N. + + Disabling this option saves about 7K of kernel size and + possibly 4K of additional runtime pagetable memory. config TOSHIBA tristate "Toshiba Laptop support"
@@ -1640,9 +1640,9 @@ config ARCH_PROC_KCORE_TEXT depends on X86_64 && PROC_KCORE config ILLEGAL_POINTER_VALUE - hex - default 0 if X86_32 - default 0xdead000000000000 if X86_64 + hex + default 0 if X86_32 + default 0xdead000000000000 if X86_64 config X86_PMEM_LEGACY_DEVICE bool
@@ -1938,11 +1938,11 @@ config EFI platforms. config EFI_STUB - bool "EFI stub support" - depends on EFI && !X86_USE_3DNOW - select RELOCATABLE - ---help--- - This kernel feature allows a bzImage to be loaded directly + bool "EFI stub support" + depends on EFI && !X86_USE_3DNOW + select RELOCATABLE + ---help--- + This kernel feature allows a bzImage to be loaded directly by EFI firmware without the use of a bootloader. See Documentation/efi-stub.txt for more information.
@@ -1951,15 +1951,15 @@ config EFI_MIXED bool "EFI mixed-mode support" depends on EFI_STUB && X86_64 ---help--- - Enabling this feature allows a 64-bit kernel to be booted - on a 32-bit firmware, provided that your CPU supports 64-bit - mode. + Enabling this feature allows a 64-bit kernel to be booted + on a 32-bit firmware, provided that your CPU supports 64-bit + mode. - Note that it is not possible to boot a mixed-mode enabled - kernel via the EFI boot stub - a bootloader that supports - the EFI handover protocol must be used. + Note that it is not possible to boot a mixed-mode enabled + kernel via the EFI boot stub - a bootloader that supports + the EFI handover protocol must be used. - If unsure, say N. + If unsure, say N. config SECCOMP def_bool y
@@ -2190,16 +2190,16 @@ config RANDOMIZE_MEMORY select DYNAMIC_MEMORY_LAYOUT default RANDOMIZE_BASE ---help--- - Randomizes the base virtual address of kernel memory sections - (physical memory mapping, vmalloc & vmemmap). This security feature - makes exploits relying on predictable memory locations less reliable. + Randomizes the base virtual address of kernel memory sections + (physical memory mapping, vmalloc & vmemmap). This security feature + makes exploits relying on predictable memory locations less reliable. - The order of allocations remains unchanged. Entropy is generated in - the same way as RANDOMIZE_BASE. Current implementation in the optimal - configuration have in average 30,000 different possible virtual - addresses for each memory section. + The order of allocations remains unchanged. Entropy is generated in + the same way as RANDOMIZE_BASE. Current implementation in the optimal + configuration have in average 30,000 different possible virtual + addresses for each memory section. - If unsure, say Y. + If unsure, say Y. config RANDOMIZE_MEMORY_PHYSICAL_PADDING hex "Physical memory mapping padding" if EXPERT
@@ -2209,12 +2209,12 @@ config RANDOMIZE_MEMORY_PHYSICAL_PADDING range 0x1 0x40 if MEMORY_HOTPLUG range 0x0 0x40 ---help--- - Define the padding in terabytes added to the existing physical - memory size during kernel memory randomization. It is useful - for memory hotplug support but reduces the entropy available for - address randomization. + Define the padding in terabytes added to the existing physical + memory size during kernel memory randomization. It is useful + for memory hotplug support but reduces the entropy available for + address randomization. - If unsure, leave at the default value. + If unsure, leave at the default value. config HOTPLUG_CPU bool "Support for hot-pluggable CPUs"
arch/x86/kvm/Kconfig +2 -2
@@ -93,8 +93,8 @@ config KVM_MMU_AUDIT bool "Audit KVM MMU" depends on KVM && TRACEPOINTS ---help--- - This option adds a R/W kVM module parameter 'mmu_audit', which allows - auditing of KVM MMU events at runtime. + This option adds a R/W kVM module parameter 'mmu_audit', which allows + auditing of KVM MMU events at runtime. # OK, it's a little counter-intuitive to do this, but it puts it neatly under # the virtualization menu.
arch/x86/xen/Kconfig +4 -4
@@ -61,10 +61,10 @@ config XEN_512GB boot parameter "xen_512gb_limit". config XEN_SAVE_RESTORE - bool - depends on XEN - select HIBERNATE_CALLBACKS - default y + bool + depends on XEN + select HIBERNATE_CALLBACKS + default y config XEN_DEBUG_FS bool "Enable Xen debug and tuning parameters in debugfs"
Signature · 1 line
1.9.1
PATCH 53/114 drivers: pinctrl: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/pinctrl/Kconfig | 18 +++++----- drivers/pinctrl/freescale/Kconfig | 13 ++++--- drivers/pinctrl/mvebu/Kconfig | 10 +++--- drivers/pinctrl/qcom/Kconfig | 74 +++++++++++++++++++-------------------- drivers/pinctrl/sh-pfc/Kconfig | 48 ++++++++++++------------- 5 files changed, 81 insertions(+), 82 deletions(-)
drivers/pinctrl/Kconfig +9 -9
@@ -31,15 +31,15 @@ config DEBUG_PINCTRL Say Y here to add some extra checks and diagnostics to PINCTRL calls. config PINCTRL_ARTPEC6 - bool "Axis ARTPEC-6 pin controller driver" - depends on MACH_ARTPEC6 - select PINMUX - select GENERIC_PINCONF - help - This is the driver for the Axis ARTPEC-6 pin controller. This driver - supports pin function multiplexing as well as pin bias and drive - strength configuration. Device tree integration instructions can be - found in Documentation/devicetree/bindings/pinctrl/axis,artpec6-pinctrl.txt + bool "Axis ARTPEC-6 pin controller driver" + depends on MACH_ARTPEC6 + select PINMUX + select GENERIC_PINCONF + help + This is the driver for the Axis ARTPEC-6 pin controller. This driver + supports pin function multiplexing as well as pin bias and drive + strength configuration. Device tree integration instructions can be + found in Documentation/devicetree/bindings/pinctrl/axis,artpec6-pinctrl.txt config PINCTRL_AS3722 tristate "Pinctrl and GPIO driver for ams AS3722 PMIC"
drivers/pinctrl/freescale/Kconfig +6 -7
@@ -36,14 +36,13 @@ config PINCTRL_IMX27 help Say Y here to enable the imx27 pinctrl driver - config PINCTRL_IMX25 - bool "IMX25 pinctrl driver" - depends on OF - depends on SOC_IMX25 - select PINCTRL_IMX - help - Say Y here to enable the imx25 pinctrl driver + bool "IMX25 pinctrl driver" + depends on OF + depends on SOC_IMX25 + select PINCTRL_IMX + help + Say Y here to enable the imx25 pinctrl driver config PINCTRL_IMX35 bool "IMX35 pinctrl driver"
drivers/pinctrl/mvebu/Kconfig +5 -5
@@ -45,8 +45,8 @@ config PINCTRL_ORION select PINCTRL_MVEBU config PINCTRL_ARMADA_37XX - bool - select GENERIC_PINCONF - select MFD_SYSCON - select PINCONF - select PINMUX + bool + select GENERIC_PINCONF + select MFD_SYSCON + select PINCONF + select PINMUX
drivers/pinctrl/qcom/Kconfig +37 -37
85 lines not on this page · raw message
drivers/pinctrl/sh-pfc/Kconfig +24 -24
76 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH 54/114 drivers: platform: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/platform/chrome/Kconfig | 24 +++--- drivers/platform/x86/Kconfig | 165 ++++++++++++++++++++-------------------- 2 files changed, 94 insertions(+), 95 deletions(-)
drivers/platform/chrome/Kconfig +12 -12
@@ -70,16 +70,16 @@ config CROS_EC_SPI 'pre-amble' bytes before the response actually starts. config CROS_EC_LPC - tristate "ChromeOS Embedded Controller (LPC)" - depends on MFD_CROS_EC && ACPI && (X86 || COMPILE_TEST) - help - If you say Y here, you get support for talking to the ChromeOS EC - over an LPC bus. This uses a simple byte-level protocol with a - checksum. This is used for userspace access only. The kernel - typically has its own communication methods. + tristate "ChromeOS Embedded Controller (LPC)" + depends on MFD_CROS_EC && ACPI && (X86 || COMPILE_TEST) + help + If you say Y here, you get support for talking to the ChromeOS EC + over an LPC bus. This uses a simple byte-level protocol with a + checksum. This is used for userspace access only. The kernel + typically has its own communication methods. - To compile this driver as a module, choose M here: the - module will be called cros_ec_lpc. + To compile this driver as a module, choose M here: the + module will be called cros_ec_lpc. config CROS_EC_LPC_MEC bool "ChromeOS Embedded Controller LPC Microchip EC (MEC) variant"
@@ -94,9 +94,9 @@ config CROS_EC_LPC_MEC choose Y here. config CROS_EC_PROTO - bool - help - ChromeOS EC communication protocol helpers. + bool + help + ChromeOS EC communication protocol helpers. config CROS_KBD_LED_BACKLIGHT tristate "Backlight LED support for Chrome OS keyboards"
drivers/platform/x86/Kconfig +82 -83
282 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH 55/114 drivers: crypto: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/crypto/Kconfig | 28 ++++++++++++++-------------- drivers/crypto/caam/Kconfig | 18 +++++++++--------- drivers/crypto/ccp/Kconfig | 10 +++++----- drivers/crypto/chelsio/Kconfig | 30 +++++++++++++++--------------- drivers/crypto/stm32/Kconfig | 6 +++--- drivers/crypto/ux500/Kconfig | 16 ++++++++-------- 6 files changed, 54 insertions(+), 54 deletions(-)
drivers/crypto/Kconfig +14 -14
@@ -18,7 +18,7 @@ config CRYPTO_DEV_PADLOCK (so called VIA PadLock ACE, Advanced Cryptography Engine) that provides instructions for very fast cryptographic operations with supported algorithms. - + The instructions are used only when the CPU supports them. Otherwise software encryption is used.
@@ -225,15 +225,15 @@ config CRYPTO_DEV_MARVELL_CESA This driver supports CPU offload through DMA transfers. config CRYPTO_DEV_NIAGARA2 - tristate "Niagara2 Stream Processing Unit driver" - select CRYPTO_DES - select CRYPTO_BLKCIPHER - select CRYPTO_HASH - select CRYPTO_MD5 - select CRYPTO_SHA1 - select CRYPTO_SHA256 - depends on SPARC64 - help + tristate "Niagara2 Stream Processing Unit driver" + select CRYPTO_DES + select CRYPTO_BLKCIPHER + select CRYPTO_HASH + select CRYPTO_MD5 + select CRYPTO_SHA1 + select CRYPTO_SHA256 + depends on SPARC64 + help Each core of a Niagara2 processor contains a Stream Processing Unit, which itself contains several cryptographic sub-units. One set provides the Modular Arithmetic Unit,
@@ -324,15 +324,15 @@ config HW_RANDOM_PPC4XX depends on CRYPTO_DEV_PPC4XX && HW_RANDOM default y ---help--- - This option provides the kernel-side support for the TRNG hardware - found in the security function of some PowerPC 4xx SoCs. + This option provides the kernel-side support for the TRNG hardware + found in the security function of some PowerPC 4xx SoCs. config CRYPTO_DEV_OMAP tristate "Support for OMAP crypto HW accelerators" depends on ARCH_OMAP2PLUS help OMAP processors have various crypto HW accelerators. Select this if - you want to use the OMAP modules for any of the crypto algorithms. + you want to use the OMAP modules for any of the crypto algorithms. if CRYPTO_DEV_OMAP
@@ -605,7 +605,7 @@ config CRYPTO_DEV_QCOM_RNG Generator hardware found on Qualcomm SoCs. To compile this driver as a module, choose M here. The - module will be called qcom-rng. If unsure, say N. + module will be called qcom-rng. If unsure, say N. config CRYPTO_DEV_VMX bool "Support for VMX cryptographic acceleration instructions"
drivers/crypto/caam/Kconfig +9 -9
@@ -129,15 +129,15 @@ config CRYPTO_DEV_FSL_CAAM_AHASH_API will be called caamhash. config CRYPTO_DEV_FSL_CAAM_PKC_API - tristate "Register public key cryptography implementations with Crypto API" - default y - select CRYPTO_RSA - help - Selecting this will allow SEC Public key support for RSA. - Supported cryptographic primitives: encryption, decryption, - signature and verification. - To compile this as a module, choose M here: the module - will be called caam_pkc. + tristate "Register public key cryptography implementations with Crypto API" + default y + select CRYPTO_RSA + help + Selecting this will allow SEC Public key support for RSA. + Supported cryptographic primitives: encryption, decryption, + signature and verification. + To compile this as a module, choose M here: the module + will be called caam_pkc. config CRYPTO_DEV_FSL_CAAM_RNG_API tristate "Register caam device for hwrng API"
drivers/crypto/ccp/Kconfig +5 -5
@@ -39,8 +39,8 @@ config CRYPTO_DEV_SP_PSP default y depends on CRYPTO_DEV_CCP_DD && X86_64 help - Provide support for the AMD Platform Security Processor (PSP). - The PSP is a dedicated processor that provides support for key - management commands in Secure Encrypted Virtualization (SEV) mode, - along with software-based Trusted Execution Environment (TEE) to - enable third-party trusted applications. + Provide support for the AMD Platform Security Processor (PSP). + The PSP is a dedicated processor that provides support for key + management commands in Secure Encrypted Virtualization (SEV) mode, + along with software-based Trusted Execution Environment (TEE) to + enable third-party trusted applications.
drivers/crypto/chelsio/Kconfig +15 -15
@@ -21,22 +21,22 @@ config CRYPTO_DEV_CHELSIO will be called chcr. config CHELSIO_IPSEC_INLINE - bool "Chelsio IPSec XFRM Tx crypto offload" - depends on CHELSIO_T4 + bool "Chelsio IPSec XFRM Tx crypto offload" + depends on CHELSIO_T4 depends on CRYPTO_DEV_CHELSIO - depends on XFRM_OFFLOAD - depends on INET_ESP_OFFLOAD || INET6_ESP_OFFLOAD - default n - ---help--- - Enable support for IPSec Tx Inline. + depends on XFRM_OFFLOAD + depends on INET_ESP_OFFLOAD || INET6_ESP_OFFLOAD + default n + ---help--- + Enable support for IPSec Tx Inline. config CRYPTO_DEV_CHELSIO_TLS - tristate "Chelsio Crypto Inline TLS Driver" - depends on CHELSIO_T4 - depends on TLS - select CRYPTO_DEV_CHELSIO - ---help--- - Support Chelsio Inline TLS with Chelsio crypto accelerator. + tristate "Chelsio Crypto Inline TLS Driver" + depends on CHELSIO_T4 + depends on TLS + select CRYPTO_DEV_CHELSIO + ---help--- + Support Chelsio Inline TLS with Chelsio crypto accelerator. - To compile this driver as a module, choose M here: the module - will be called chtls. + To compile this driver as a module, choose M here: the module + will be called chtls.
drivers/crypto/stm32/Kconfig +3 -3
@@ -3,7 +3,7 @@ config CRYPTO_DEV_STM32_CRC depends on ARCH_STM32 select CRYPTO_HASH help - This enables support for the CRC32 hw accelerator which can be found + This enables support for the CRC32 hw accelerator which can be found on STMicroelectronics STM32 SOC. config CRYPTO_DEV_STM32_HASH
@@ -16,7 +16,7 @@ config CRYPTO_DEV_STM32_HASH select CRYPTO_SHA256 select CRYPTO_ENGINE help - This enables support for the HASH hw accelerator which can be found + This enables support for the HASH hw accelerator which can be found on STMicroelectronics STM32 SOC. config CRYPTO_DEV_STM32_CRYP
@@ -25,5 +25,5 @@ config CRYPTO_DEV_STM32_CRYP select CRYPTO_HASH select CRYPTO_ENGINE help - This enables support for the CRYP (AES/DES/TDES) hw accelerator which + This enables support for the CRYP (AES/DES/TDES) hw accelerator which can be found on STMicroelectronics STM32 SOC.
drivers/crypto/ux500/Kconfig +8 -8
@@ -11,18 +11,18 @@ config CRYPTO_DEV_UX500_CRYP select CRYPTO_BLKCIPHER select CRYPTO_DES help - This selects the crypto driver for the UX500_CRYP hardware. It supports - AES-ECB, CBC and CTR with keys sizes of 128, 192 and 256 bit sizes. + This selects the crypto driver for the UX500_CRYP hardware. It supports + AES-ECB, CBC and CTR with keys sizes of 128, 192 and 256 bit sizes. config CRYPTO_DEV_UX500_HASH - tristate "UX500 crypto driver for HASH block" - depends on CRYPTO_DEV_UX500 - select CRYPTO_HASH + tristate "UX500 crypto driver for HASH block" + depends on CRYPTO_DEV_UX500 + select CRYPTO_HASH select CRYPTO_SHA1 select CRYPTO_SHA256 - help - This selects the hash driver for the UX500_HASH hardware. - Depends on UX500/STM DMA if running in DMA mode. + help + This selects the hash driver for the UX500_HASH hardware. + Depends on UX500/STM DMA if running in DMA mode. config CRYPTO_DEV_UX500_DEBUG bool "Activate ux500 platform debug-mode for crypto and hash block"
Signature · 1 line
1.9.1
PATCH 56/114 drivers: spi: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/spi/Kconfig | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-)
drivers/spi/Kconfig +12 -12
@@ -142,7 +142,7 @@ config SPI_BCM63XX tristate "Broadcom BCM63xx SPI controller" depends on BCM63XX || COMPILE_TEST help - Enable support for the SPI controller on the Broadcom BCM63xx SoCs. + Enable support for the SPI controller on the Broadcom BCM63xx SoCs. config SPI_BCM63XX_HSSPI tristate "Broadcom BCM63XX HS SPI controller driver"
@@ -230,14 +230,14 @@ config SPI_DW_MMIO depends on SPI_DESIGNWARE config SPI_DLN2 - tristate "Diolan DLN-2 USB SPI adapter" - depends on MFD_DLN2 - help - If you say yes to this option, support will be included for Diolan - DLN2, a USB to SPI interface. + tristate "Diolan DLN-2 USB SPI adapter" + depends on MFD_DLN2 + help + If you say yes to this option, support will be included for Diolan + DLN2, a USB to SPI interface. - This driver can also be built as a module. If so, the module - will be called spi-dln2. + This driver can also be built as a module. If so, the module + will be called spi-dln2. config SPI_EFM32 tristate "EFM32 SPI controller"
@@ -727,10 +727,10 @@ config SPI_SUN6I This enables using the SPI controller on the Allwinner A31 SoCs. config SPI_MXIC - tristate "Macronix MX25F0A SPI controller" - depends on SPI_MASTER - help - This selects the Macronix MX25F0A SPI controller driver. + tristate "Macronix MX25F0A SPI controller" + depends on SPI_MASTER + help + This selects the Macronix MX25F0A SPI controller driver. config SPI_MXS tristate "Freescale MXS SPI controller"
Signature · 1 line
1.9.1
PATCH 57/114 drivers: power: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/power/avs/Kconfig | 12 +++++------ drivers/power/supply/Kconfig | 48 ++++++++++++++++++++++---------------------- 2 files changed, 30 insertions(+), 30 deletions(-)
drivers/power/avs/Kconfig +6 -6
@@ -12,9 +12,9 @@ menuconfig POWER_AVS Say Y here to enable Adaptive Voltage Scaling class support. config ROCKCHIP_IODOMAIN - tristate "Rockchip IO domain support" - depends on POWER_AVS && ARCH_ROCKCHIP && OF - help - Say y here to enable support io domains on Rockchip SoCs. It is - necessary for the io domain setting of the SoC to match the - voltage supplied by the regulators. + tristate "Rockchip IO domain support" + depends on POWER_AVS && ARCH_ROCKCHIP && OF + help + Say y here to enable support io domains on Rockchip SoCs. It is + necessary for the io domain setting of the SoC to match the + voltage supplied by the regulators.
drivers/power/supply/Kconfig +24 -24
98 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH 58/114 drivers: net: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/net/Kconfig | 64 ++++++------- drivers/net/appletalk/Kconfig | 1 - drivers/net/arcnet/Kconfig | 26 ++--- drivers/net/caif/Kconfig | 36 +++---- drivers/net/can/usb/Kconfig | 8 +- drivers/net/ethernet/allwinner/Kconfig | 10 +- drivers/net/ethernet/aurora/Kconfig | 2 +- drivers/net/ethernet/dec/tulip/Kconfig | 6 +- drivers/net/ethernet/emulex/benet/Kconfig | 2 +- drivers/net/ethernet/freescale/fs_enet/Kconfig | 8 +- drivers/net/ethernet/intel/Kconfig | 6 +- drivers/net/ethernet/marvell/Kconfig | 9 +- drivers/net/ethernet/mellanox/mlx5/core/Kconfig | 36 +++---- drivers/net/ethernet/mellanox/mlxsw/Kconfig | 4 +- drivers/net/ethernet/microchip/Kconfig | 12 +-- drivers/net/ethernet/nxp/Kconfig | 8 +- drivers/net/hamradio/Kconfig | 1 - drivers/net/ieee802154/Kconfig | 12 +-- drivers/net/phy/Kconfig | 6 +- drivers/net/usb/Kconfig | 10 +- drivers/net/wan/Kconfig | 4 +- drivers/net/wireless/ath/Kconfig | 12 +-- drivers/net/wireless/ath/ar5523/Kconfig | 14 +-- drivers/net/wireless/ath/ath9k/Kconfig | 45 ++++----- drivers/net/wireless/ath/carl9170/Kconfig | 6 +- drivers/net/wireless/atmel/Kconfig | 54 +++++------ drivers/net/wireless/intel/ipw2x00/Kconfig | 120 ++++++++++++------------ drivers/net/wireless/intel/iwlegacy/Kconfig | 6 +- drivers/net/wireless/intel/iwlwifi/Kconfig | 31 +++--- drivers/net/wireless/intersil/p54/Kconfig | 16 ++-- drivers/net/wireless/ralink/rt2x00/Kconfig | 47 +++++----- drivers/net/wireless/rsi/Kconfig | 4 +- drivers/net/wireless/ti/wl12xx/Kconfig | 8 +- 33 files changed, 316 insertions(+), 318 deletions(-)
drivers/net/Kconfig +32 -32
@@ -152,22 +152,22 @@ config IPVLAN_L3S select NET_L3_MASTER_DEV config IPVLAN - tristate "IP-VLAN support" - depends on INET - depends on IPV6 || !IPV6 - ---help--- - This allows one to create virtual devices off of a main interface - and packets will be delivered based on the dest L3 (IPv6/IPv4 addr) - on packets. All interfaces (including the main interface) share L2 - making it transparent to the connected L2 switch. + tristate "IP-VLAN support" + depends on INET + depends on IPV6 || !IPV6 + ---help--- + This allows one to create virtual devices off of a main interface + and packets will be delivered based on the dest L3 (IPv6/IPv4 addr) + on packets. All interfaces (including the main interface) share L2 + making it transparent to the connected L2 switch. - Ipvlan devices can be added using the "ip" command from the - iproute2 package starting with the iproute2-3.19 release: + Ipvlan devices can be added using the "ip" command from the + iproute2 package starting with the iproute2-3.19 release: - "ip link add link <main-dev> [ NAME ] type ipvlan" + "ip link add link <main-dev> [ NAME ] type ipvlan" - To compile this driver as a module, choose M here: the module - will be called ipvlan. + To compile this driver as a module, choose M here: the module + will be called ipvlan. config IPVTAP tristate "IP-VLAN based tap driver"
@@ -184,11 +184,11 @@ config IPVTAP will be called ipvtap. config VXLAN - tristate "Virtual eXtensible Local Area Network (VXLAN)" - depends on INET - select NET_UDP_TUNNEL - select GRO_CELLS - ---help--- + tristate "Virtual eXtensible Local Area Network (VXLAN)" + depends on INET + select NET_UDP_TUNNEL + select GRO_CELLS + ---help--- This allows one to create vxlan virtual interfaces that provide Layer 2 Networks over Layer 3 Networks. VXLAN is often used to tunnel virtual network infrastructure in virtualized environments.
@@ -199,12 +199,12 @@ config VXLAN will be called vxlan. config GENEVE - tristate "Generic Network Virtualization Encapsulation" - depends on INET - depends on IPV6 || !IPV6 - select NET_UDP_TUNNEL - select GRO_CELLS - ---help--- + tristate "Generic Network Virtualization Encapsulation" + depends on INET + depends on IPV6 || !IPV6 + select NET_UDP_TUNNEL + select GRO_CELLS + ---help--- This allows one to create geneve virtual interfaces that provide Layer 2 Networks over Layer 3 Networks. GENEVE is often used to tunnel virtual network infrastructure in virtualized environments.
@@ -238,7 +238,7 @@ config MACSEC select CRYPTO_GCM select GRO_CELLS ---help--- - MACsec is an encryption standard for Ethernet. + MACsec is an encryption standard for Ethernet. config NETCONSOLE tristate "Network console logging support"
@@ -361,12 +361,12 @@ config NET_VRF support enables VRF devices. config VSOCKMON - tristate "Virtual vsock monitoring device" - depends on VHOST_VSOCK - ---help--- - This option enables a monitoring net device for vsock sockets. It is - mostly intended for developers or support to debug vsock issues. If - unsure, say N. + tristate "Virtual vsock monitoring device" + depends on VHOST_VSOCK + ---help--- + This option enables a monitoring net device for vsock sockets. It is + mostly intended for developers or support to debug vsock issues. If + unsure, say N. endif # NET_CORE
@@ -486,7 +486,7 @@ config FUJITSU_ES depends on ACPI help This driver provides support for Extended Socket network device - on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series. + on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series. config THUNDERBOLT_NET tristate "Networking over Thunderbolt cable"
drivers/net/appletalk/Kconfig +0 -1
@@ -36,7 +36,6 @@ config DEV_APPLETALK on a network. If your Linux box is connected to such a network, and wish to do IP over it, or you have a LocalTalk card and wish to use it to connect to the AppleTalk network, say Y. - config LTPC tristate "Apple/Farallon LocalTalk PC support"
drivers/net/arcnet/Kconfig +13 -13
@@ -55,19 +55,19 @@ config ARCNET_CAP tristate "Enable CAP mode packet interface" help ARCnet "cap mode" packet encapsulation. Used to get the hardware - acknowledge back to userspace. After the initial protocol byte every - packet is stuffed with an extra 4 byte "cookie" which doesn't - actually appear on the network. After transmit the driver will send - back a packet with protocol byte 0 containing the status of the - transmission: - 0=no hardware acknowledge - 1=excessive nak - 2=transmission accepted by the receiver hardware - - Received packets are also stuffed with the extra 4 bytes but it will - be random data. - - Cap only listens to protocol 1-8. + acknowledge back to userspace. After the initial protocol byte every + packet is stuffed with an extra 4 byte "cookie" which doesn't + actually appear on the network. After transmit the driver will send + back a packet with protocol byte 0 containing the status of the + transmission: + 0=no hardware acknowledge + 1=excessive nak + 2=transmission accepted by the receiver hardware + + Received packets are also stuffed with the extra 4 bytes but it will + be random data. + + Cap only listens to protocol 1-8. config ARCNET_COM90xx tristate "ARCnet COM90xx (normal) chipset driver"
drivers/net/caif/Kconfig +18 -18
@@ -9,37 +9,37 @@ config CAIF_TTY depends on CAIF && TTY default n ---help--- - The CAIF TTY transport driver is a Line Discipline (ldisc) - identified as N_CAIF. When this ldisc is opened from user space - it will redirect the TTY's traffic into the CAIF stack. + The CAIF TTY transport driver is a Line Discipline (ldisc) + identified as N_CAIF. When this ldisc is opened from user space + it will redirect the TTY's traffic into the CAIF stack. config CAIF_SPI_SLAVE tristate "CAIF SPI transport driver for slave interface" depends on CAIF && HAS_DMA default n ---help--- - The CAIF Link layer SPI Protocol driver for Slave SPI interface. - This driver implements a platform driver to accommodate for a - platform specific SPI device. A sample CAIF SPI Platform device is - provided in Documentation/networking/caif/spi_porting.txt + The CAIF Link layer SPI Protocol driver for Slave SPI interface. + This driver implements a platform driver to accommodate for a + platform specific SPI device. A sample CAIF SPI Platform device is + provided in Documentation/networking/caif/spi_porting.txt config CAIF_SPI_SYNC bool "Next command and length in start of frame" depends on CAIF_SPI_SLAVE default n ---help--- - Putting the next command and length in the start of the frame can - help to synchronize to the next transfer in case of over or under-runs. - This option also needs to be enabled on the modem. + Putting the next command and length in the start of the frame can + help to synchronize to the next transfer in case of over or under-runs. + This option also needs to be enabled on the modem. config CAIF_HSI - tristate "CAIF HSI transport driver" - depends on CAIF - default n - ---help--- - The caif low level driver for CAIF over HSI. - Be aware that if you enable this then you also need to - enable a low-level HSI driver. + tristate "CAIF HSI transport driver" + depends on CAIF + default n + ---help--- + The caif low level driver for CAIF over HSI. + Be aware that if you enable this then you also need to + enable a low-level HSI driver. config CAIF_VIRTIO tristate "CAIF virtio transport driver"
@@ -49,7 +49,7 @@ config CAIF_VIRTIO select GENERIC_ALLOCATOR default n ---help--- - The caif driver for CAIF over Virtio. + The caif driver for CAIF over Virtio. if CAIF_VIRTIO source "drivers/vhost/Kconfig.vringh"
drivers/net/can/usb/Kconfig +4 -4
@@ -14,10 +14,10 @@ config CAN_EMS_USB from EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de). config CAN_ESD_USB2 - tristate "ESD USB/2 CAN/USB interface" - ---help--- - This driver supports the CAN-USB/2 interface - from esd electronic system design gmbh (http://www.esd.eu). + tristate "ESD USB/2 CAN/USB interface" + ---help--- + This driver supports the CAN-USB/2 interface + from esd electronic system design gmbh (http://www.esd.eu). config CAN_GS_USB tristate "Geschwister Schneider UG interfaces"
drivers/net/ethernet/allwinner/Kconfig +5 -5
@@ -20,17 +20,17 @@ config NET_VENDOR_ALLWINNER if NET_VENDOR_ALLWINNER config SUN4I_EMAC - tristate "Allwinner A10 EMAC support" + tristate "Allwinner A10 EMAC support" depends on ARCH_SUNXI depends on OF select CRC32 select MII select PHYLIB select MDIO_SUN4I - ---help--- - Support for Allwinner A10 EMAC ethernet driver. + ---help--- + Support for Allwinner A10 EMAC ethernet driver. - To compile this driver as a module, choose M here. The module - will be called sun4i-emac. + To compile this driver as a module, choose M here. The module + will be called sun4i-emac. endif # NET_VENDOR_ALLWINNER
drivers/net/ethernet/aurora/Kconfig +1 -1
@@ -17,6 +17,6 @@ config AURORA_NB8800 depends on HAS_DMA select PHYLIB help - Support for the AU-NB8800 gigabit Ethernet controller. + Support for the AU-NB8800 gigabit Ethernet controller. endif
drivers/net/ethernet/dec/tulip/Kconfig +3 -3
@@ -44,7 +44,7 @@ config TULIP select CRC32 ---help--- This driver is developed for the SMC EtherPower series Ethernet - cards and also works with cards based on the DECchip + cards and also works with cards based on the DECchip 21140 (Tulip series) chips. Some LinkSys PCI cards are of this type. (If your card is NOT SMC EtherPower 10/100 PCI (smc9332dst), you can also try the driver for "Generic DECchip"
@@ -124,7 +124,7 @@ config WINBOND_840 select CRC32 select MII ---help--- - This driver is for the Winbond W89c840 chip. It also works with + This driver is for the Winbond W89c840 chip. It also works with the TX9882 chip on the Compex RL100-ATX board. More specific information and updates are available from <http://www.scyld.com/network/drivers.html>.
@@ -152,7 +152,7 @@ config ULI526X To compile this driver as a module, choose M here. The module will be called uli526x. - + config PCMCIA_XIRCOM tristate "Xircom CardBus support" depends on CARDBUS
drivers/net/ethernet/emulex/benet/Kconfig +1 -1
@@ -47,5 +47,5 @@ config BE2NET_SKYHAWK chipsets. (e.g. OneConnect OCe14xxx) comment "WARNING: be2net is useless without any enabled chip" - depends on BE2NET_BE2=n && BE2NET_BE3=n && BE2NET_LANCER=n && \ + depends on BE2NET_BE2=n && BE2NET_BE3=n && BE2NET_LANCER=n && \ BE2NET_SKYHAWK=n && BE2NET
drivers/net/ethernet/freescale/fs_enet/Kconfig +4 -4
@@ -1,8 +1,8 @@ config FS_ENET - tristate "Freescale Ethernet Driver" - depends on NET_VENDOR_FREESCALE && (CPM1 || CPM2 || PPC_MPC512x) - select MII - select PHYLIB + tristate "Freescale Ethernet Driver" + depends on NET_VENDOR_FREESCALE && (CPM1 || CPM2 || PPC_MPC512x) + select MII + select PHYLIB config FS_ENET_MPC5121_FEC def_bool y if (FS_ENET && PPC_MPC512x)
drivers/net/ethernet/intel/Kconfig +3 -3
@@ -79,9 +79,9 @@ config E1000E_HWTS default y depends on E1000E && X86 ---help--- - Say Y to enable hardware supported cross-timestamping on PCH - devices. The cross-timestamp is available through the PTP clock - driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE). + Say Y to enable hardware supported cross-timestamping on PCH + devices. The cross-timestamp is available through the PTP clock + driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE). config IGB tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support"
drivers/net/ethernet/marvell/Kconfig +4 -5
@@ -136,10 +136,10 @@ config SKGE_GENESIS bool "Support for older SysKonnect Genesis boards" depends on SKGE ---help--- - This enables support for the older and uncommon SysKonnect Genesis - chips, which support MII via an external transceiver, instead of - an internal one. Disabling this option will save some memory - by making code smaller. If unsure say Y. + This enables support for the older and uncommon SysKonnect Genesis + chips, which support MII via an external transceiver, instead of + an internal one. Disabling this option will save some memory + by making code smaller. If unsure say Y. config SKY2 tristate "Marvell Yukon 2 support"
@@ -167,7 +167,6 @@ config SKY2_DEBUG If unsure, say N. - source "drivers/net/ethernet/marvell/octeontx2/Kconfig" endif # NET_VENDOR_MARVELL
drivers/net/ethernet/mellanox/mlx5/core/Kconfig +18 -18
@@ -16,15 +16,15 @@ config MLX5_ACCEL bool config MLX5_FPGA - bool "Mellanox Technologies Innova support" - depends on MLX5_CORE + bool "Mellanox Technologies Innova support" + depends on MLX5_CORE select MLX5_ACCEL - ---help--- - Build support for the Innova family of network cards by Mellanox - Technologies. Innova network cards are comprised of a ConnectX chip - and an FPGA chip on one board. If you select this option, the - mlx5_core driver will include the Innova FPGA core and allow building - sandbox-specific client drivers. + ---help--- + Build support for the Innova family of network cards by Mellanox + Technologies. Innova network cards are comprised of a ConnectX chip + and an FPGA chip on one board. If you select this option, the + mlx5_core driver will include the Innova FPGA core and allow building + sandbox-specific client drivers. config MLX5_CORE_EN bool "Mellanox 5th generation network adapters (ConnectX series) Ethernet support"
@@ -54,14 +54,14 @@ config MLX5_EN_RXNFC API. config MLX5_MPFS - bool "Mellanox Technologies MLX5 MPFS support" - depends on MLX5_CORE_EN + bool "Mellanox Technologies MLX5 MPFS support" + depends on MLX5_CORE_EN default y - ---help--- + ---help--- Mellanox Technologies Ethernet Multi-Physical Function Switch (MPFS) - support in ConnectX NIC. MPFs is required for when multi-PF configuration - is enabled to allow passing user configured unicast MAC addresses to the - requesting PF. + support in ConnectX NIC. MPFs is required for when multi-PF configuration + is enabled to allow passing user configured unicast MAC addresses to the + requesting PF. config MLX5_ESWITCH bool "Mellanox Technologies MLX5 SRIOV E-Switch support"
@@ -69,10 +69,10 @@ config MLX5_ESWITCH default y ---help--- Mellanox Technologies Ethernet SRIOV E-Switch support in ConnectX NIC. - E-Switch provides internal SRIOV packet steering and switching for the - enabled VFs and PF in two available modes: - Legacy SRIOV mode (L2 mac vlan steering based). - Switchdev mode (eswitch offloads). + E-Switch provides internal SRIOV packet steering and switching for the + enabled VFs and PF in two available modes: + Legacy SRIOV mode (L2 mac vlan steering based). + Switchdev mode (eswitch offloads). config MLX5_CORE_EN_DCB bool "Data Center Bridging (DCB) Support"
drivers/net/ethernet/mellanox/mlxsw/Kconfig +2 -2
@@ -24,8 +24,8 @@ config MLXSW_CORE_THERMAL depends on !(MLXSW_CORE=y && THERMAL=m) default y ---help--- - Say Y here if you want to automatically control fans speed according - ambient temperature reported by ASIC. + Say Y here if you want to automatically control fans speed according + ambient temperature reported by ASIC. config MLXSW_PCI tristate "PCI bus implementation for Mellanox Technologies Switch ASICs"
drivers/net/ethernet/microchip/Kconfig +6 -6
@@ -33,13 +33,13 @@ config ENC28J60_WRITEVERIFY If unsure, say N. config ENCX24J600 - tristate "ENCX24J600 support" - depends on SPI - ---help--- - Support for the Microchip ENC424J600/624J600 ethernet chip. + tristate "ENCX24J600 support" + depends on SPI + ---help--- + Support for the Microchip ENC424J600/624J600 ethernet chip. - To compile this driver as a module, choose M here. The module will be - called encx24j600. + To compile this driver as a module, choose M here. The module will be + called encx24j600. config LAN743X tristate "LAN743x support"
drivers/net/ethernet/nxp/Kconfig +4 -4
@@ -1,8 +1,8 @@ config LPC_ENET - tristate "NXP ethernet MAC on LPC devices" - depends on ARCH_LPC32XX - select PHYLIB - help + tristate "NXP ethernet MAC on LPC devices" + depends on ARCH_LPC32XX + select PHYLIB + help Say Y or M here if you want to use the NXP ethernet MAC included on some NXP LPC devices. You can safely enable this option for LPC32xx SoC. Also available as a module.
drivers/net/hamradio/Kconfig +0 -1
@@ -190,4 +190,3 @@ config YAM To compile this driver as a module, choose M here: the module will be called yam. -
drivers/net/ieee802154/Kconfig +6 -6
@@ -73,9 +73,9 @@ config IEEE802154_ATUSB The module will be called 'atusb'. config IEEE802154_ADF7242 - tristate "ADF7242 transceiver driver" - depends on IEEE802154_DRIVERS && MAC802154 - depends on SPI + tristate "ADF7242 transceiver driver" + depends on IEEE802154_DRIVERS && MAC802154 + depends on SPI ---help--- Say Y here to enable the ADF7242 SPI 802.15.4 wireless controller.
@@ -106,9 +106,9 @@ config IEEE802154_CA8210_DEBUGFS management entities. config IEEE802154_MCR20A - tristate "MCR20A transceiver driver" - depends on IEEE802154_DRIVERS && MAC802154 - depends on SPI + tristate "MCR20A transceiver driver" + depends on IEEE802154_DRIVERS && MAC802154 + depends on SPI ---help--- Say Y here to enable the MCR20A SPI 802.15.4 wireless controller.
drivers/net/phy/Kconfig +3 -3
@@ -417,9 +417,9 @@ config RENESAS_PHY Supports the Renesas PHYs uPD60620 and uPD60620A. config ROCKCHIP_PHY - tristate "Driver for Rockchip Ethernet PHYs" - ---help--- - Currently supports the integrated Ethernet PHY. + tristate "Driver for Rockchip Ethernet PHYs" + ---help--- + Currently supports the integrated Ethernet PHY. config SMSC_PHY tristate "SMSC PHYs"
drivers/net/usb/Kconfig +5 -5
@@ -168,7 +168,7 @@ config USB_NET_AX8817X This option adds support for ASIX AX88xxx based USB 2.0 10/100 Ethernet adapters. - This driver should work with at least the following devices: + This driver should work with at least the following devices: * Aten UC210T * ASIX AX88172 * Billionton Systems, USB2AR
@@ -219,13 +219,13 @@ config USB_NET_CDCETHER CDC Ethernet is an implementation option for DOCSIS cable modems that support USB connectivity, used for non-Microsoft USB hosts. The Linux-USB CDC Ethernet Gadget driver is an open implementation. - This driver should work with at least the following devices: + This driver should work with at least the following devices: * Dell Wireless 5530 HSPA - * Ericsson PipeRider (all variants) + * Ericsson PipeRider (all variants) * Ericsson Mobile Broadband Module (all variants) - * Motorola (DM100 and SB4100) - * Broadcom Cable Modem (reference design) + * Motorola (DM100 and SB4100) + * Broadcom Cable Modem (reference design) * Toshiba (PCX1100U and F3507g/F3607gw) * ...
drivers/net/wan/Kconfig +2 -2
@@ -48,7 +48,7 @@ config COSA network device. You will need user-space utilities COSA or SRP boards for downloading - the firmware to the cards and to set them up. Look at the + the firmware to the cards and to set them up. Look at the <http://www.fi.muni.cz/~kas/cosa/> for more information. You can also read the comment at the top of the <file:drivers/net/wan/cosa.c> for details about the cards and the driver itself.
@@ -107,7 +107,7 @@ config HDLC Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame Relay, synchronous Point-to-Point Protocol (PPP) and X.25. - To compile this driver as a module, choose M here: the + To compile this driver as a module, choose M here: the module will be called hdlc. If unsure, say N.
drivers/net/wireless/ath/Kconfig +6 -6
@@ -29,12 +29,12 @@ config ATH_DEBUG Right now only ath9k makes use of this. config ATH_TRACEPOINTS - bool "Atheros wireless tracing" - depends on ATH_DEBUG - depends on EVENT_TRACING - ---help--- - This option enables tracepoints for atheros wireless drivers. - Currently, ath9k makes use of this facility. + bool "Atheros wireless tracing" + depends on ATH_DEBUG + depends on EVENT_TRACING + ---help--- + This option enables tracepoints for atheros wireless drivers. + Currently, ath9k makes use of this facility. config ATH_REG_DYNAMIC_USER_REG_HINTS bool "Atheros dynamic user regulatory hints"
drivers/net/wireless/ath/ar5523/Kconfig +7 -7
@@ -1,8 +1,8 @@ config AR5523 - tristate "Atheros AR5523 wireless driver support" - depends on MAC80211 && USB - select ATH_COMMON - select FW_LOADER - ---help--- - This module add support for AR5523 based USB dongles such as D-Link - DWL-G132, Netgear WPN111 and many more. + tristate "Atheros AR5523 wireless driver support" + depends on MAC80211 && USB + select ATH_COMMON + select FW_LOADER + ---help--- + This module add support for AR5523 based USB dongles such as D-Link + DWL-G132, Netgear WPN111 and many more.
drivers/net/wireless/ath/ath9k/Kconfig +24 -21
67 lines not on this page · raw message
drivers/net/wireless/ath/carl9170/Kconfig +3 -3
@@ -40,9 +40,9 @@ config CARL9170_WPC default y config CARL9170_HWRNG - bool "Random number generator" - depends on CARL9170 && (HW_RANDOM = y || HW_RANDOM = CARL9170) - default n + bool "Random number generator" + depends on CARL9170 && (HW_RANDOM = y || HW_RANDOM = CARL9170) + default n help Provides a hardware random number generator to the kernel.
drivers/net/wireless/atmel/Kconfig +27 -27
67 lines not on this page · raw message
drivers/net/wireless/intel/ipw2x00/Kconfig +60 -60
188 lines not on this page · raw message
drivers/net/wireless/intel/iwlegacy/Kconfig +3 -3
@@ -90,9 +90,9 @@ config IWLEGACY_DEBUG any problems you may encounter. config IWLEGACY_DEBUGFS - bool "iwlegacy (iwl 3945/4965) debugfs support" - depends on IWLEGACY && MAC80211_DEBUGFS - ---help--- + bool "iwlegacy (iwl 3945/4965) debugfs support" + depends on IWLEGACY && MAC80211_DEBUGFS + ---help--- Enable creation of debugfs files for the iwlegacy drivers. This is a low-impact option that allows getting insight into the driver's state at runtime.
drivers/net/wireless/intel/iwlwifi/Kconfig +15 -16
@@ -24,7 +24,6 @@ config IWLWIFI Intel 8260 Wi-Fi Adapter Intel 3165 Wi-Fi Adapter - This driver uses the kernel's mac80211 subsystem. In order to use this driver, you will need a firmware
@@ -92,18 +91,18 @@ config IWLWIFI_BCAST_FILTERING expect incoming broadcasts for their normal operations. config IWLWIFI_PCIE_RTPM - bool "Enable runtime power management mode for PCIe devices" - depends on IWLMVM && PM && EXPERT - help - Say Y here to enable runtime power management for PCIe - devices. If enabled, the device will go into low power mode - when idle for a short period of time, allowing for improved - power saving during runtime. Note that this feature requires - a tight integration with the platform. It is not recommended - to enable this feature without proper validation with the - specific target platform. - - If unsure, say N. + bool "Enable runtime power management mode for PCIe devices" + depends on IWLMVM && PM && EXPERT + help + Say Y here to enable runtime power management for PCIe + devices. If enabled, the device will go into low power mode + when idle for a short period of time, allowing for improved + power saving during runtime. Note that this feature requires + a tight integration with the platform. It is not recommended + to enable this feature without proper validation with the + specific target platform. + + If unsure, say N. menu "Debugging Options"
@@ -132,9 +131,9 @@ config IWLWIFI_DEBUG any problems you may encounter. config IWLWIFI_DEBUGFS - bool "iwlwifi debugfs support" - depends on MAC80211_DEBUGFS - ---help--- + bool "iwlwifi debugfs support" + depends on MAC80211_DEBUGFS + ---help--- Enable creation of debugfs files for the iwlwifi drivers. This is a low-impact option that allows getting insight into the driver's state at runtime.
drivers/net/wireless/intersil/p54/Kconfig +8 -8
@@ -53,17 +53,17 @@ config P54_SPI_DEFAULT_EEPROM depends on P54_SPI default n ---help--- - Unlike the PCI or USB devices, the SPI variants don't have - a dedicated EEPROM chip to store all device specific values - for calibration, country and interface settings. + Unlike the PCI or USB devices, the SPI variants don't have + a dedicated EEPROM chip to store all device specific values + for calibration, country and interface settings. - The driver will try to load the image "3826.eeprom", if the - file is put at the right place. (usually /lib/firmware.) + The driver will try to load the image "3826.eeprom", if the + file is put at the right place. (usually /lib/firmware.) - Only if this request fails, this option will provide a - backup set of generic values to get the device working. + Only if this request fails, this option will provide a + backup set of generic values to get the device working. - Enabling this option adds about 4k to p54spi. + Enabling this option adds about 4k to p54spi. config P54_LEDS bool
drivers/net/wireless/ralink/rt2x00/Kconfig +23 -24
75 lines not on this page · raw message
drivers/net/wireless/rsi/Kconfig +2 -2
@@ -24,8 +24,8 @@ config RSI_DEBUGFS depends on RSI_91X default y ---help--- - Say Y, if you would like to enable debug support. This option - creates debugfs entries + Say Y, if you would like to enable debug support. This option + creates debugfs entries config RSI_SDIO tristate "Redpine Signals SDIO bus support"
drivers/net/wireless/ti/wl12xx/Kconfig +4 -4
@@ -1,9 +1,9 @@ config WL12XX - tristate "TI wl12xx support" + tristate "TI wl12xx support" depends on MAC80211 - select WLCORE - ---help--- + select WLCORE + ---help--- This module adds support for wireless adapters based on TI wl1271, wl1273, wl1281 and wl1283 chipsets. This module does *not* include support for wl1251. For wl1251 support, use the separate homonymous - driver instead. + driver instead.
Signature · 1 line
1.9.1
PATCH 59/114 drivers: phy: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/phy/hisilicon/Kconfig | 16 ++++++++-------- drivers/phy/mediatek/Kconfig | 20 ++++++++++---------- 2 files changed, 18 insertions(+), 18 deletions(-)
drivers/phy/hisilicon/Kconfig +8 -8
@@ -22,14 +22,14 @@ config PHY_HISTB_COMBPHY If unsure, say N. config PHY_HISI_INNO_USB2 - tristate "HiSilicon INNO USB2 PHY support" - depends on (ARCH_HISI && ARM64) || COMPILE_TEST - select GENERIC_PHY - select MFD_SYSCON - help - Support for INNO USB2 PHY on HiSilicon SoCs. This Phy supports - USB 1.5Mb/s, USB 12Mb/s, USB 480Mb/s speeds. It supports one - USB host port to accept one USB device. + tristate "HiSilicon INNO USB2 PHY support" + depends on (ARCH_HISI && ARM64) || COMPILE_TEST + select GENERIC_PHY + select MFD_SYSCON + help + Support for INNO USB2 PHY on HiSilicon SoCs. This Phy supports + USB 1.5Mb/s, USB 12Mb/s, USB 480Mb/s speeds. It supports one + USB host port to accept one USB device. config PHY_HIX5HD2_SATA tristate "HIX5HD2 SATA PHY Driver"
drivers/phy/mediatek/Kconfig +10 -10
@@ -2,22 +2,22 @@ # Phy drivers for Mediatek devices # config PHY_MTK_TPHY - tristate "MediaTek T-PHY Driver" - depends on ARCH_MEDIATEK && OF - select GENERIC_PHY - help - Say 'Y' here to add support for MediaTek T-PHY driver, - it supports multiple usb2.0, usb3.0 ports, PCIe and + tristate "MediaTek T-PHY Driver" + depends on ARCH_MEDIATEK && OF + select GENERIC_PHY + help + Say 'Y' here to add support for MediaTek T-PHY driver, + it supports multiple usb2.0, usb3.0 ports, PCIe and SATA, and meanwhile supports two version T-PHY which have different banks layout, the T-PHY with shared banks between multi-ports is first version, otherwise is second veriosn, so you can easily distinguish them by banks layout. config PHY_MTK_XSPHY - tristate "MediaTek XS-PHY Driver" - depends on ARCH_MEDIATEK && OF - select GENERIC_PHY - help + tristate "MediaTek XS-PHY Driver" + depends on ARCH_MEDIATEK && OF + select GENERIC_PHY + help Enable this to support the SuperSpeedPlus XS-PHY transceiver for USB3.1 GEN2 controllers on MediaTek chips. The driver supports multiple USB2.0, USB3.1 GEN2 ports.
Signature · 1 line
1.9.1
PATCH 60/114 drivers: pci: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/pci/Kconfig | 40 +++++++++++++++++----------------- drivers/pci/controller/Kconfig | 14 ++++++------ drivers/pci/controller/dwc/Kconfig | 6 ++--- drivers/pci/endpoint/Kconfig | 20 ++++++++--------- drivers/pci/endpoint/functions/Kconfig | 6 ++--- drivers/pci/hotplug/Kconfig | 2 +- drivers/pci/switch/Kconfig | 10 ++++----- 7 files changed, 49 insertions(+), 49 deletions(-)
drivers/pci/Kconfig +20 -20
@@ -40,16 +40,16 @@ config PCI_MSI bool "Message Signaled Interrupts (MSI and MSI-X)" select GENERIC_MSI_IRQ help - This allows device drivers to enable MSI (Message Signaled - Interrupts). Message Signaled Interrupts enable a device to - generate an interrupt using an inbound Memory Write on its - PCI bus instead of asserting a device IRQ pin. + This allows device drivers to enable MSI (Message Signaled + Interrupts). Message Signaled Interrupts enable a device to + generate an interrupt using an inbound Memory Write on its + PCI bus instead of asserting a device IRQ pin. - Use of PCI MSI interrupts can be disabled at kernel boot time - by using the 'pci=nomsi' option. This disables MSI for the - entire system. + Use of PCI MSI interrupts can be disabled at kernel boot time + by using the 'pci=nomsi' option. This disables MSI for the + entire system. - If you don't know what to do here, say Y. + If you don't know what to do here, say Y. config PCI_MSI_IRQ_DOMAIN def_bool ARC || ARM || ARM64 || X86
@@ -106,14 +106,14 @@ config PCI_PF_STUB When in doubt, say N. config XEN_PCIDEV_FRONTEND - tristate "Xen PCI Frontend" - depends on X86 && XEN - select PCI_XEN + tristate "Xen PCI Frontend" + depends on X86 && XEN + select PCI_XEN select XEN_XENBUS_FRONTEND - default y - help - The PCI device frontend driver allows the kernel to import arbitrary - PCI devices from a PCI backend to support PCI driver domains. + default y + help + The PCI device frontend driver allows the kernel to import arbitrary + PCI devices from a PCI backend to support PCI driver domains. config PCI_ATS bool
@@ -180,11 +180,11 @@ config PCI_LABEL select NLS config PCI_HYPERV - tristate "Hyper-V PCI Frontend" - depends on X86 && HYPERV && PCI_MSI && PCI_MSI_IRQ_DOMAIN && X86_64 - help - The PCI device frontend driver allows the kernel to import arbitrary - PCI devices from a PCI backend to support PCI driver domains. + tristate "Hyper-V PCI Frontend" + depends on X86 && HYPERV && PCI_MSI && PCI_MSI_IRQ_DOMAIN && X86_64 + help + The PCI device frontend driver allows the kernel to import arbitrary + PCI devices from a PCI backend to support PCI driver domains. source "drivers/pci/hotplug/Kconfig" source "drivers/pci/controller/Kconfig"
drivers/pci/controller/Kconfig +7 -7
@@ -18,9 +18,9 @@ config PCI_AARDVARK depends on PCI_MSI_IRQ_DOMAIN select PCI_BRIDGE_EMUL help - Add support for Aardvark 64bit PCIe Host Controller. This - controller is part of the South Bridge of the Marvel Armada - 3700 SoC. + Add support for Aardvark 64bit PCIe Host Controller. This + controller is part of the South Bridge of the Marvel Armada + 3700 SoC. menu "Cadence PCIe controllers support"
@@ -55,10 +55,10 @@ config PCIE_XILINX_NWL depends on ARCH_ZYNQMP || COMPILE_TEST depends on PCI_MSI_IRQ_DOMAIN help - Say 'Y' here if you want kernel support for Xilinx - NWL PCIe controller. The controller can act as Root Port - or End Point. The current option selection will only - support root port enabling. + Say 'Y' here if you want kernel support for Xilinx + NWL PCIe controller. The controller can act as Root Port + or End Point. The current option selection will only + support root port enabling. config PCI_FTPCI100 bool "Faraday Technology FTPCI100 PCI controller"
drivers/pci/controller/dwc/Kconfig +3 -3
@@ -7,9 +7,9 @@ config PCIE_DW bool config PCIE_DW_HOST - bool + bool depends on PCI_MSI_IRQ_DOMAIN - select PCIE_DW + select PCIE_DW config PCIE_DW_EP bool
@@ -191,7 +191,7 @@ config PCIE_HISI_STB depends on PCI_MSI_IRQ_DOMAIN select PCIE_DW_HOST help - Say Y here if you want PCIe controller support on HiSilicon STB SoCs + Say Y here if you want PCIe controller support on HiSilicon STB SoCs config PCI_MESON bool "MESON PCIe controller"
drivers/pci/endpoint/Kconfig +10 -10
@@ -9,24 +9,24 @@ config PCI_ENDPOINT bool "PCI Endpoint Support" depends on HAVE_PCI help - Enable this configuration option to support configurable PCI - endpoint. This should be enabled if the platform has a PCI - controller that can operate in endpoint mode. + Enable this configuration option to support configurable PCI + endpoint. This should be enabled if the platform has a PCI + controller that can operate in endpoint mode. - Enabling this option will build the endpoint library, which - includes endpoint controller library and endpoint function - library. + Enabling this option will build the endpoint library, which + includes endpoint controller library and endpoint function + library. - If in doubt, say "N" to disable Endpoint support. + If in doubt, say "N" to disable Endpoint support. config PCI_ENDPOINT_CONFIGFS bool "PCI Endpoint Configfs Support" depends on PCI_ENDPOINT select CONFIGFS_FS help - This will enable the configfs entry that can be used to - configure the endpoint function and used to bind the - function with a endpoint controller. + This will enable the configfs entry that can be used to + configure the endpoint function and used to bind the + function with a endpoint controller. source "drivers/pci/endpoint/functions/Kconfig"
drivers/pci/endpoint/functions/Kconfig +3 -3
@@ -8,7 +8,7 @@ config PCI_EPF_TEST depends on PCI_ENDPOINT select CRC32 help - Enable this configuration option to enable the test driver - for PCI Endpoint. + Enable this configuration option to enable the test driver + for PCI Endpoint. - If in doubt, say "N" to disable Endpoint test driver. + If in doubt, say "N" to disable Endpoint test driver.
drivers/pci/hotplug/Kconfig +1 -1
@@ -83,7 +83,7 @@ config HOTPLUG_PCI_CPCI_ZT5550 depends on HOTPLUG_PCI_CPCI && X86 help Say Y here if you have an Performance Technologies (formerly Intel, - formerly just Ziatech) Ziatech ZT5550 CompactPCI system card. + formerly just Ziatech) Ziatech ZT5550 CompactPCI system card. To compile this driver as a module, choose M here: the module will be called cpcihp_zt5550.
drivers/pci/switch/Kconfig +5 -5
@@ -6,10 +6,10 @@ menu "PCI switch controller drivers" config PCI_SW_SWITCHTEC tristate "MicroSemi Switchtec PCIe Switch Management Driver" help - Enables support for the management interface for the MicroSemi - Switchtec series of PCIe switches. Supports userspace access - to submit MRPC commands to the switch via /dev/switchtecX - devices. See <file:Documentation/switchtec.txt> for more - information. + Enables support for the management interface for the MicroSemi + Switchtec series of PCIe switches. Supports userspace access + to submit MRPC commands to the switch via /dev/switchtecX + devices. See <file:Documentation/switchtec.txt> for more + information. endmenu
Signature · 1 line
1.9.1
PATCH 61/114 drivers: sbus: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/sbus/char/Kconfig | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
drivers/sbus/char/Kconfig +3 -4
@@ -68,9 +68,8 @@ config ORACLE_DAX depends on SPARC64 default m help - Driver for Oracle Data Analytics Accelerator, which is - a coprocessor that performs database operations in hardware. - It is available on M7 and M8 based systems only. + Driver for Oracle Data Analytics Accelerator, which is + a coprocessor that performs database operations in hardware. + It is available on M7 and M8 based systems only. endmenu -
Signature · 1 line
1.9.1
PATCH 62/114 init: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- init/Kconfig | 103 +++++++++++++++++++++++++++++------------------------------ 1 file changed, 51 insertions(+), 52 deletions(-)
init/Kconfig +51 -52
@@ -39,7 +39,7 @@ config BUILDTIME_EXTABLE_SORT config THREAD_INFO_IN_TASK bool help - Select this to move thread_info off the stack into task_struct. To + Select this to move thread_info off the stack into task_struct. To make this work, an arch will need to remove all thread_info fields except flags and fix any runtime bugs.
@@ -111,13 +111,13 @@ config LOCALVERSION_AUTO which is done within the script "scripts/setlocalversion".) config BUILD_SALT - string "Build ID Salt" - default "" - help - The build ID is used to link binaries and their debug info. Setting - this option will use the value in the calculation of the build id. - This is mostly useful for distributions which want to ensure the - build is unique between builds. It's safe to leave the default. + string "Build ID Salt" + default "" + help + The build ID is used to link binaries and their debug info. Setting + this option will use the value in the calculation of the build id. + This is mostly useful for distributions which want to ensure the + build is unique between builds. It's safe to leave the default. config HAVE_KERNEL_GZIP bool
@@ -718,7 +718,7 @@ menuconfig CGROUPS if CGROUPS config PAGE_COUNTER - bool + bool config MEMCG bool "Memory controller"
@@ -1193,9 +1193,9 @@ menuconfig EXPERT select DEBUG_KERNEL help This option allows certain base kernel options and settings - to be disabled or tweaked. This is for specialized - environments which can tolerate a "non-standard" kernel. - Only use this if you really know what you are doing. + to be disabled or tweaked. This is for specialized + environments which can tolerate a "non-standard" kernel. + Only use this if you really know what you are doing. config UID16 bool "Enable 16-bit UID system calls" if EXPERT
@@ -1305,11 +1305,11 @@ config BUG bool "BUG() support" if EXPERT default y help - Disabling this option eliminates support for BUG and WARN, reducing - the size of your kernel image and potentially quietly ignoring - numerous fatal conditions. You should only consider disabling this - option for embedded systems with no facilities for reporting errors. - Just say Y. + Disabling this option eliminates support for BUG and WARN, reducing + the size of your kernel image and potentially quietly ignoring + numerous fatal conditions. You should only consider disabling this + option for embedded systems with no facilities for reporting errors. + Just say Y. config ELF_CORE depends on COREDUMP
@@ -1318,15 +1318,14 @@ config ELF_CORE help Enable support for generating core dumps. Disabling saves about 4k. - config PCSPKR_PLATFORM bool "Enable PC-Speaker support" if EXPERT depends on HAVE_PCSPKR_PLATFORM select I8253_LOCK default y help - This option allows to disable the internal PC-Speaker - support, saving some memory. + This option allows to disable the internal PC-Speaker + support, saving some memory. config BASE_FULL default y
@@ -1447,29 +1446,29 @@ config MEMBARRIER If unsure, say Y. config KALLSYMS - bool "Load all symbols for debugging/ksymoops" if EXPERT - default y - help - Say Y here to let the kernel print out symbolic crash information and - symbolic stack backtraces. This increases the size of the kernel - somewhat, as all symbols have to be loaded into the kernel image. + bool "Load all symbols for debugging/ksymoops" if EXPERT + default y + help + Say Y here to let the kernel print out symbolic crash information and + symbolic stack backtraces. This increases the size of the kernel + somewhat, as all symbols have to be loaded into the kernel image. config KALLSYMS_ALL bool "Include all symbols in kallsyms" depends on DEBUG_KERNEL && KALLSYMS help - Normally kallsyms only contains the symbols of functions for nicer - OOPS messages and backtraces (i.e., symbols from the text and inittext - sections). This is sufficient for most cases. And only in very rare - cases (e.g., when a debugger is used) all symbols are required (e.g., - names of variables from the data sections, etc). + Normally kallsyms only contains the symbols of functions for nicer + OOPS messages and backtraces (i.e., symbols from the text and inittext + sections). This is sufficient for most cases. And only in very rare + cases (e.g., when a debugger is used) all symbols are required (e.g., + names of variables from the data sections, etc). - This option makes sure that all symbols are loaded into the kernel - image (i.e., symbols from all sections) in cost of increased kernel - size (depending on the kernel configuration, it may be 300KiB or - something like this). + This option makes sure that all symbols are loaded into the kernel + image (i.e., symbols from all sections) in cost of increased kernel + size (depending on the kernel configuration, it may be 300KiB or + something like this). - Say N unless you really need all symbols. + Say N unless you really need all symbols. config KALLSYMS_ABSOLUTE_PERCPU bool
@@ -1615,12 +1614,12 @@ config DEBUG_PERF_USE_VMALLOC depends on PERF_EVENTS && DEBUG_KERNEL && !PPC select PERF_USE_VMALLOC help - Use vmalloc memory to back perf mmap() buffers. + Use vmalloc memory to back perf mmap() buffers. - Mostly useful for debugging the vmalloc code on platforms - that don't require it. + Mostly useful for debugging the vmalloc code on platforms + that don't require it. - Say N if unsure. + Say N if unsure. endmenu
@@ -1673,7 +1672,7 @@ choice prompt "Choose SLAB allocator" default SLUB help - This option allows to select a slab allocator. + This option allows to select a slab allocator. config SLAB bool "SLAB"
@@ -1687,20 +1686,20 @@ config SLUB bool "SLUB (Unqueued Allocator)" select HAVE_HARDENED_USERCOPY_ALLOCATOR help - SLUB is a slab allocator that minimizes cache line usage - instead of managing queues of cached objects (SLAB approach). - Per cpu caching is realized using slabs of objects instead - of queues of objects. SLUB can use memory efficiently - and has enhanced diagnostics. SLUB is the default choice for - a slab allocator. + SLUB is a slab allocator that minimizes cache line usage + instead of managing queues of cached objects (SLAB approach). + Per cpu caching is realized using slabs of objects instead + of queues of objects. SLUB can use memory efficiently + and has enhanced diagnostics. SLUB is the default choice for + a slab allocator. config SLOB depends on EXPERT bool "SLOB (Simple Allocator)" help - SLOB replaces the stock allocator with a drastically simpler - allocator. SLOB is generally more space efficient but - does not perform as well on large systems. + SLOB replaces the stock allocator with a drastically simpler + allocator. SLOB is generally more space efficient but + does not perform as well on large systems. endchoice
@@ -1800,7 +1799,7 @@ config PROFILING config TRACEPOINTS bool -endmenu # General setup +endmenu # General setup source "arch/Kconfig"
@@ -1880,7 +1879,7 @@ config MODULE_SRCVERSION_ALL help Modules which contain a MODULE_VERSION get an extra "srcversion" field inserted into their modinfo section, which contains a - sum of the source files which made it. This helps maintainers + sum of the source files which made it. This helps maintainers see exactly which source was used to build a module (since others sometimes change the module source without updating the version). With this option, such a "srcversion" field
Signature · 1 line
1.9.1
PATCH 63/114 drivers: media: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/media/i2c/Kconfig | 6 +- drivers/media/platform/Kconfig | 150 +++++------ drivers/media/platform/am437x/Kconfig | 8 +- drivers/media/platform/atmel/Kconfig | 4 +- drivers/media/platform/davinci/Kconfig | 50 ++-- drivers/media/platform/exynos4-is/Kconfig | 2 +- drivers/media/platform/sunxi/sun6i-csi/Kconfig | 2 +- drivers/media/platform/xilinx/Kconfig | 4 +- drivers/media/radio/si470x/Kconfig | 4 +- drivers/media/rc/Kconfig | 343 ++++++++++++------------- drivers/media/rc/img-ir/Kconfig | 52 ++-- 11 files changed, 308 insertions(+), 317 deletions(-)
drivers/media/i2c/Kconfig +3 -3
@@ -1113,10 +1113,10 @@ config VIDEO_M52790 tristate "Mitsubishi M52790 A/V switch" depends on VIDEO_V4L2 && I2C ---help--- - Support for the Mitsubishi M52790 A/V switch. + Support for the Mitsubishi M52790 A/V switch. - To compile this driver as a module, choose M here: the - module will be called m52790. + To compile this driver as a module, choose M here: the + module will be called m52790. config VIDEO_I2C tristate "I2C transport video support"
drivers/media/platform/Kconfig +75 -75
234 lines not on this page · raw message
drivers/media/platform/am437x/Kconfig +4 -4
@@ -5,8 +5,8 @@ config VIDEO_AM437X_VPFE select VIDEOBUF2_DMA_CONTIG select V4L2_FWNODE help - Support for AM437x Video Processing Front End based Video - Capture Driver. + Support for AM437x Video Processing Front End based Video + Capture Driver. - To compile this driver as a module, choose M here. The module - will be called am437x-vpfe. + To compile this driver as a module, choose M here. The module + will be called am437x-vpfe.
drivers/media/platform/atmel/Kconfig +2 -2
@@ -6,8 +6,8 @@ config VIDEO_ATMEL_ISC select REGMAP_MMIO select V4L2_FWNODE help - This module makes the ATMEL Image Sensor Controller available - as a v4l2 device. + This module makes the ATMEL Image Sensor Controller available + as a v4l2 device. config VIDEO_ATMEL_ISI tristate "ATMEL Image Sensor Interface (ISI) support"
drivers/media/platform/davinci/Kconfig +25 -25
75 lines not on this page · raw message
drivers/media/platform/exynos4-is/Kconfig +1 -1
@@ -12,7 +12,7 @@ config VIDEO_SAMSUNG_EXYNOS4_IS if VIDEO_SAMSUNG_EXYNOS4_IS config VIDEO_EXYNOS4_IS_COMMON - tristate + tristate config VIDEO_S5P_FIMC tristate "S5P/EXYNOS4 FIMC/CAMIF camera interface driver"
drivers/media/platform/sunxi/sun6i-csi/Kconfig +1 -1
@@ -6,4 +6,4 @@ config VIDEO_SUN6I_CSI select REGMAP_MMIO select V4L2_FWNODE help - Support for the Allwinner Camera Sensor Interface Controller on V3s. + Support for the Allwinner Camera Sensor Interface Controller on V3s.
drivers/media/platform/xilinx/Kconfig +2 -2
@@ -15,12 +15,12 @@ config VIDEO_XILINX_TPG depends on VIDEO_XILINX select VIDEO_XILINX_VTC ---help--- - Driver for the Xilinx Video Test Pattern Generator + Driver for the Xilinx Video Test Pattern Generator config VIDEO_XILINX_VTC tristate "Xilinx Video Timing Controller" depends on VIDEO_XILINX ---help--- - Driver for the Xilinx Video Timing Controller + Driver for the Xilinx Video Timing Controller endif #VIDEO_XILINX
drivers/media/radio/si470x/Kconfig +2 -2
@@ -1,6 +1,6 @@ config RADIO_SI470X - tristate "Silicon Labs Si470x FM Radio Receiver support" - depends on VIDEO_V4L2 + tristate "Silicon Labs Si470x FM Radio Receiver support" + depends on VIDEO_V4L2 ---help--- This is a driver for devices with the Silicon Labs SI470x chip (either via USB or I2C buses).
drivers/media/rc/Kconfig +167 -176
624 lines not on this page · raw message
drivers/media/rc/img-ir/Kconfig +26 -26
100 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH 64/114 drivers: parisc: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/parisc/Kconfig | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/parisc/Kconfig +1 -2
@@ -123,9 +123,8 @@ config PDC_CHASSIS shown by the LED/LCD driver. This driver updates the state panel (LED and/or LCD) upon system state change (eg: boot, shutdown or panic). - - If unsure, say Y. + If unsure, say Y. config PDC_CHASSIS_WARN bool "PDC chassis warnings support"
Signature · 1 line
1.9.1
PATCH 65/114 drivers: regulator: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/regulator/Kconfig | 49 +++++++++++++++++++++++------------------------ 1 file changed, 24 insertions(+), 25 deletions(-)
drivers/regulator/Kconfig +24 -25
@@ -123,9 +123,9 @@ config REGULATOR_AB3100 depends on AB3100_CORE default y if AB3100_CORE help - These regulators correspond to functionality in the - AB3100 analog baseband dealing with power regulators - for the system. + These regulators correspond to functionality in the + AB3100 analog baseband dealing with power regulators + for the system. config REGULATOR_AB8500 bool "ST-Ericsson AB8500 Power Regulators"
@@ -378,15 +378,15 @@ config REGULATOR_LP3971 tristate "National Semiconductors LP3971 PMIC regulator driver" depends on I2C help - Say Y here to support the voltage regulators and convertors - on National Semiconductors LP3971 PMIC + Say Y here to support the voltage regulators and convertors + on National Semiconductors LP3971 PMIC config REGULATOR_LP3972 tristate "National Semiconductors LP3972 PMIC regulator driver" depends on I2C help - Say Y here to support the voltage regulators and convertors - on National Semiconductors LP3972 PMIC + Say Y here to support the voltage regulators and convertors + on National Semiconductors LP3972 PMIC config REGULATOR_LP872X tristate "TI/National Semiconductor LP8720/LP8725 voltage regulators"
@@ -649,24 +649,24 @@ config REGULATOR_PBIAS tristate "PBIAS OMAP regulator driver" depends on (ARCH_OMAP || COMPILE_TEST) && MFD_SYSCON help - Say y here to support pbias regulator for mmc1:SD card i/o - on OMAP SoCs. - This driver provides support for OMAP pbias modelled - regulators. + Say y here to support pbias regulator for mmc1:SD card i/o + on OMAP SoCs. + This driver provides support for OMAP pbias modelled + regulators. config REGULATOR_PCAP tristate "Motorola PCAP2 regulator driver" depends on EZX_PCAP help - This driver provides support for the voltage regulators of the - PCAP2 PMIC. + This driver provides support for the voltage regulators of the + PCAP2 PMIC. config REGULATOR_PCF50633 tristate "NXP PCF50633 regulator driver" depends on MFD_PCF50633 help - Say Y here to support the voltage regulators and converters - on PCF50633 + Say Y here to support the voltage regulators and converters + on PCF50633 config REGULATOR_PFUZE100 tristate "Freescale PFUZE100/200/3000/3001 regulator driver"
@@ -789,25 +789,25 @@ config REGULATOR_S2MPA01 tristate "Samsung S2MPA01 voltage regulator" depends on MFD_SEC_CORE help - This driver controls Samsung S2MPA01 voltage output regulator - via I2C bus. S2MPA01 has 10 Bucks and 26 LDO outputs. + This driver controls Samsung S2MPA01 voltage output regulator + via I2C bus. S2MPA01 has 10 Bucks and 26 LDO outputs. config REGULATOR_S2MPS11 tristate "Samsung S2MPS11/13/14/15/S2MPU02 voltage regulator" depends on MFD_SEC_CORE help - This driver supports a Samsung S2MPS11/13/14/15/S2MPU02 voltage - output regulator via I2C bus. The chip is comprised of high efficient - Buck converters including Dual-Phase Buck converter, Buck-Boost - converter, various LDOs. + This driver supports a Samsung S2MPS11/13/14/15/S2MPU02 voltage + output regulator via I2C bus. The chip is comprised of high efficient + Buck converters including Dual-Phase Buck converter, Buck-Boost + converter, various LDOs. config REGULATOR_S5M8767 tristate "Samsung S5M8767A voltage regulator" depends on MFD_SEC_CORE help - This driver supports a Samsung S5M8767A voltage output regulator - via I2C bus. S5M8767A have 9 Bucks and 28 LDOs output and - supports DVS mode with 8bits of output voltage control. + This driver supports a Samsung S5M8767A voltage output regulator + via I2C bus. S5M8767A have 9 Bucks and 28 LDOs output and + supports DVS mode with 8bits of output voltage control. config REGULATOR_SC2731 tristate "Spreadtrum SC2731 power regulator driver"
@@ -1058,4 +1058,3 @@ config REGULATOR_WM8994 WM8994 CODEC. endif -
Signature · 1 line
1.9.1
PATCH 66/114 drivers: mtd: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/mtd/nand/onenand/Kconfig | 12 ++++---- drivers/mtd/ubi/Kconfig | 60 ++++++++++++++++++++-------------------- 2 files changed, 36 insertions(+), 36 deletions(-)
drivers/mtd/nand/onenand/Kconfig +6 -6
@@ -32,12 +32,12 @@ config MTD_ONENAND_OMAP2 Enable dmaengine and gpiolib for better performance. config MTD_ONENAND_SAMSUNG - tristate "OneNAND on Samsung SOC controller support" - depends on ARCH_S3C64XX || ARCH_S5PV210 || ARCH_EXYNOS4 - help - Support for a OneNAND flash device connected to an Samsung SOC. - S3C64XX uses command mapping method. - S5PC110/S5PC210 use generic OneNAND method. + tristate "OneNAND on Samsung SOC controller support" + depends on ARCH_S3C64XX || ARCH_S5PV210 || ARCH_EXYNOS4 + help + Support for a OneNAND flash device connected to an Samsung SOC. + S3C64XX uses command mapping method. + S5PC110/S5PC210 use generic OneNAND method. config MTD_ONENAND_OTP bool "OneNAND OTP Support"
drivers/mtd/ubi/Kconfig +30 -30
77 lines not on this page · raw message
Signature · 1 line
1.9.1
PATCH 67/114 drivers: i2c: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/i2c/Kconfig | 2 +- drivers/i2c/busses/Kconfig | 36 ++++++++++++++++++------------------ drivers/i2c/muxes/Kconfig | 18 +++++++++--------- 3 files changed, 28 insertions(+), 28 deletions(-)
drivers/i2c/Kconfig +1 -1
@@ -55,7 +55,7 @@ config I2C_CHARDEV programs use the I2C bus. Information on how to do this is contained in the file <file:Documentation/i2c/dev-interface>. - This support is also available as a module. If so, the module + This support is also available as a module. If so, the module will be called i2c-dev. config I2C_MUX
drivers/i2c/busses/Kconfig +18 -18
@@ -277,7 +277,7 @@ config I2C_VIA select I2C_ALGOBIT help If you say yes to this option, support will be included for the VIA - 82C586B I2C interface + 82C586B I2C interface This driver can also be built as a module. If so, the module will be called i2c-via.
@@ -647,11 +647,11 @@ config I2C_IMX_LPI2C tristate "IMX Low Power I2C interface" depends on ARCH_MXC || COMPILE_TEST help - Say Y here if you want to use the Low Power IIC bus controller - on the Freescale i.MX processors. + Say Y here if you want to use the Low Power IIC bus controller + on the Freescale i.MX processors. - This driver can also be built as a module. If so, the module - will be called i2c-imx-lpi2c. + This driver can also be built as a module. If so, the module + will be called i2c-imx-lpi2c. config I2C_IOP3XX tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
@@ -667,10 +667,10 @@ config I2C_JZ4780 tristate "JZ4780 I2C controller interface support" depends on MACH_JZ4780 || COMPILE_TEST help - If you say yes to this option, support will be included for the - Ingenic JZ4780 I2C controller. + If you say yes to this option, support will be included for the + Ingenic JZ4780 I2C controller. - If you don't know what to do here, say N. + If you don't know what to do here, say N. config I2C_KEMPLD tristate "Kontron COM I2C Controller"
@@ -1145,14 +1145,14 @@ config I2C_DIOLAN_U2C will be called i2c-diolan-u2c. config I2C_DLN2 - tristate "Diolan DLN-2 USB I2C adapter" - depends on MFD_DLN2 - help - If you say yes to this option, support will be included for Diolan - DLN2, a USB to I2C interface. + tristate "Diolan DLN-2 USB I2C adapter" + depends on MFD_DLN2 + help + If you say yes to this option, support will be included for Diolan + DLN2, a USB to I2C interface. - This driver can also be built as a module. If so, the module - will be called i2c-dln2. + This driver can also be built as a module. If so, the module + will be called i2c-dln2. config I2C_PARPORT tristate "Parallel port adapter"
@@ -1246,9 +1246,9 @@ config I2C_VIPERBOARD help Say yes here to access the I2C part of the Nano River Technologies Viperboard as I2C master. - See viperboard API specification and Nano - River Tech's viperboard.h for detailed meaning - of the module parameters. + See viperboard API specification and Nano + River Tech's viperboard.h for detailed meaning + of the module parameters. comment "Other I2C/SMBus bus drivers"
drivers/i2c/muxes/Kconfig +9 -9
@@ -108,14 +108,14 @@ config I2C_DEMUX_PINCTRL want to change the I2C master at run-time depending on features. config I2C_MUX_MLXCPLD - tristate "Mellanox CPLD based I2C multiplexer" - help - If you say yes to this option, support will be included for a - CPLD based I2C multiplexer. This driver provides access to - I2C busses connected through a MUX, which is controlled - by a CPLD register. - - This driver can also be built as a module. If so, the module - will be called i2c-mux-mlxcpld. + tristate "Mellanox CPLD based I2C multiplexer" + help + If you say yes to this option, support will be included for a + CPLD based I2C multiplexer. This driver provides access to + I2C busses connected through a MUX, which is controlled + by a CPLD register. + + This driver can also be built as a module. If so, the module + will be called i2c-mux-mlxcpld. endmenu
Signature · 1 line
1.9.1
PATCH 68/114 drivers: mfd: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/mfd/Kconfig | 62 ++++++++++++++++++++++++++--------------------------- 1 file changed, 31 insertions(+), 31 deletions(-)
drivers/mfd/Kconfig +31 -31
@@ -16,7 +16,7 @@ config MFD_CS5535 depends on PCI && (X86_32 || (X86 && COMPILE_TEST)) ---help--- This is the core driver for CS5535/CS5536 MFD functions. This is - necessary for using the board's GPIO and MFGPT functionality. + necessary for using the board's GPIO and MFGPT functionality. config MFD_ALTERA_A10SR bool "Altera Arria10 DevKit System Resource chip"
@@ -213,13 +213,13 @@ config MFD_CROS_EC protocol for talking to the EC is defined by the bus driver. config MFD_CROS_EC_CHARDEV - tristate "Chrome OS Embedded Controller userspace device interface" - depends on MFD_CROS_EC - ---help--- - This driver adds support to talk with the ChromeOS EC from userspace. + tristate "Chrome OS Embedded Controller userspace device interface" + depends on MFD_CROS_EC + ---help--- + This driver adds support to talk with the ChromeOS EC from userspace. - If you have a supported Chromebook, choose Y or M here. - The module will be called cros_ec_dev. + If you have a supported Chromebook, choose Y or M here. + The module will be called cros_ec_dev. config MFD_MADERA tristate "Cirrus Logic Madera codecs"
@@ -867,7 +867,7 @@ config MFD_CPCAP At least Motorola Droid 4 is known to use CPCAP. config MFD_VIPERBOARD - tristate "Nano River Technologies Viperboard" + tristate "Nano River Technologies Viperboard" select MFD_CORE depends on USB default n
@@ -903,15 +903,15 @@ config PCF50633_ADC tristate "NXP PCF50633 ADC" depends on MFD_PCF50633 help - Say yes here if you want to include support for ADC in the - NXP PCF50633 chip. + Say yes here if you want to include support for ADC in the + NXP PCF50633 chip. config PCF50633_GPIO tristate "NXP PCF50633 GPIO" depends on MFD_PCF50633 help - Say yes here if you want to include support GPIO for pins on - the PCF50633 chip. + Say yes here if you want to include support GPIO for pins on + the PCF50633 chip. config UCB1400_CORE tristate "Philips UCB1400 Core driver"
@@ -1026,7 +1026,7 @@ config MFD_RN5T618 select REGMAP_I2C help Say yes here to add support for the Ricoh RN5T567, - RN5T618, RC5T619 PMIC. + RN5T618, RC5T619 PMIC. This driver provides common support for accessing the device, additional drivers must be enabled in order to use the functionality of the device.
@@ -1079,9 +1079,9 @@ config MFD_SM501_GPIO bool "Export GPIO via GPIO layer" depends on MFD_SM501 && GPIOLIB ---help--- - This option uses the gpio library layer to export the 64 GPIO - lines on the SM501. The platform data is used to supply the - base number for the first GPIO line to register. + This option uses the gpio library layer to export the 64 GPIO + lines on the SM501. The platform data is used to supply the + base number for the first GPIO line to register. config MFD_SKY81452 tristate "Skyworks Solutions SKY81452"
@@ -1096,16 +1096,16 @@ config MFD_SKY81452 will be called sky81452. config MFD_SMSC - bool "SMSC ECE1099 series chips" - depends on I2C=y - select MFD_CORE - select REGMAP_I2C - help - If you say yes here you get support for the - ece1099 chips from SMSC. + bool "SMSC ECE1099 series chips" + depends on I2C=y + select MFD_CORE + select REGMAP_I2C + help + If you say yes here you get support for the + ece1099 chips from SMSC. - To compile this driver as a module, choose M here: the - module will be called smsc. + To compile this driver as a module, choose M here: the + module will be called smsc. config MFD_SC27XX_PMIC tristate "Spreadtrum SC27xx PMICs"
@@ -1171,12 +1171,12 @@ config AB8500_CORE This chip embeds various other multimedia funtionalities as well. config AB8500_DEBUG - bool "Enable debug info via debugfs" - depends on AB8500_GPADC && DEBUG_FS - default y if DEBUG_FS - help - Select this option if you want debug information using the debug - filesystem, debugfs. + bool "Enable debug info via debugfs" + depends on AB8500_GPADC && DEBUG_FS + default y if DEBUG_FS + help + Select this option if you want debug information using the debug + filesystem, debugfs. config AB8500_GPADC bool "ST-Ericsson AB8500 GPADC driver"
Signature · 1 line
1.9.1
Lee Jones
AppliedRe: [PATCH 068/114] drivers: mfd: Kconfig: pedantic formatting
Quoted 7 lines · metux IT consult
Formatting of
Kconfigfiles doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.Signed-off-by Enrico Weigelt, metux IT consult <[email protected]>--- drivers/mfd/Kconfig | 62 ++++++++++++++++++++++++++--------------------------- 1 file changed, 31 insertions(+), 31 deletions(-)
Applied, thanks.
Signature · 4 lines
Lee Jones [李琼斯] Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog
PATCH 69/114 drivers: perf: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/perf/Kconfig | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-)
drivers/perf/Kconfig +17 -17
@@ -62,11 +62,11 @@ config ARM_DSU_PMU to DSU. config HISI_PMU - bool "HiSilicon SoC PMU" - depends on ARM64 && ACPI - help - Support for HiSilicon SoC uncore performance monitoring - unit (PMU), such as: L3C, HHA and DDRC. + bool "HiSilicon SoC PMU" + depends on ARM64 && ACPI + help + Support for HiSilicon SoC uncore performance monitoring + unit (PMU), such as: L3C, HHA and DDRC. config QCOM_L2_PMU bool "Qualcomm Technologies L2-cache PMU"
@@ -82,26 +82,26 @@ config QCOM_L3_PMU depends on ARCH_QCOM && ARM64 && ACPI select QCOM_IRQ_COMBINER help - Provides support for the L3 cache performance monitor unit (PMU) - in Qualcomm Technologies processors. - Adds the L3 cache PMU into the perf events subsystem for - monitoring L3 cache events. + Provides support for the L3 cache performance monitor unit (PMU) + in Qualcomm Technologies processors. + Adds the L3 cache PMU into the perf events subsystem for + monitoring L3 cache events. config THUNDERX2_PMU tristate "Cavium ThunderX2 SoC PMU UNCORE" depends on ARCH_THUNDER2 && ARM64 && ACPI && NUMA default m help - Provides support for ThunderX2 UNCORE events. - The SoC has PMU support in its L3 cache controller (L3C) and - in the DDR4 Memory Controller (DMC). + Provides support for ThunderX2 UNCORE events. + The SoC has PMU support in its L3 cache controller (L3C) and + in the DDR4 Memory Controller (DMC). config XGENE_PMU - depends on ARCH_XGENE - bool "APM X-Gene SoC PMU" - default n - help - Say y if you want to use APM X-Gene SoC performance monitors. + depends on ARCH_XGENE + bool "APM X-Gene SoC PMU" + default n + help + Say y if you want to use APM X-Gene SoC performance monitors. config ARM_SPE_PMU tristate "Enable support for the ARMv8.2 Statistical Profiling Extension"
Signature · 1 line
1.9.1
PATCH 70/114 drivers: hwtracing: coresight: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/hwtracing/coresight/Kconfig | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/hwtracing/coresight/Kconfig +6 -6
@@ -35,12 +35,12 @@ config CORESIGHT_CATU bool "Coresight Address Translation Unit (CATU) driver" depends on CORESIGHT_LINK_AND_SINK_TMC help - Enable support for the Coresight Address Translation Unit (CATU). - CATU supports a scatter gather table of 4K pages, with forward/backward - lookup. CATU helps TMC ETR to use a large physically non-contiguous trace - buffer by translating the addresses used by ETR to the physical address - by looking up the provided table. CATU can also be used in pass-through - mode where the address is not translated. + Enable support for the Coresight Address Translation Unit (CATU). + CATU supports a scatter gather table of 4K pages, with forward/backward + lookup. CATU helps TMC ETR to use a large physically non-contiguous trace + buffer by translating the addresses used by ETR to the physical address + by looking up the provided table. CATU can also be used in pass-through + mode where the address is not translated. config CORESIGHT_SINK_TPIU bool "Coresight generic TPIU driver"
Signature · 1 line
1.9.1
PATCH 71/114 drivers: isdn: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/isdn/hardware/mISDN/Kconfig | 2 +- drivers/isdn/hisax/Kconfig | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
drivers/isdn/hardware/mISDN/Kconfig +1 -1
@@ -9,7 +9,7 @@ config MISDN_HFCPCI depends on PCI help Enable support for cards with Cologne Chip AG's - HFC PCI chip. + HFC PCI chip. config MISDN_HFCMULTI tristate "Support for HFC multiport cards (HFC-4S/8S/E1)"
drivers/isdn/hisax/Kconfig +2 -2
@@ -82,7 +82,7 @@ config HISAX_MAX_CARDS default "8" help This option allows you to specify the maximum number of cards which - the HiSax driver will be able to handle. + the HiSax driver will be able to handle. comment "HiSax supported cards"
@@ -352,7 +352,7 @@ config HISAX_DEBUG bool "HiSax debugging" help This enables debugging code in the new-style HiSax drivers, i.e. - the ST5481 USB driver currently. + the ST5481 USB driver currently. If in doubt, say yes. comment "HiSax PCMCIA card service modules"
Signature · 1 line
1.9.1
PATCH 72/114 drivers: macintosh: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/macintosh/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/macintosh/Kconfig +3 -3
@@ -177,7 +177,7 @@ config THERM_ADT746X depends on I2C && I2C_POWERMAC && PPC_PMAC && !PPC_PMAC64 help This driver provides some thermostat and fan control for the - iBook G4, and the ATI based aluminium PowerBooks, allowing slightly + iBook G4, and the ATI based aluminium PowerBooks, allowing slightly better fan behaviour by default, and some manual control. config WINDFARM
@@ -213,7 +213,7 @@ config WINDFARM_PM91 select I2C_POWERMAC help This driver provides thermal control for the PowerMac9,1 - which is the recent (SMU based) single CPU desktop G5 + which is the recent (SMU based) single CPU desktop G5 config WINDFARM_PM112 tristate "Support for thermal management on PowerMac11,2"
@@ -241,7 +241,7 @@ config PMAC_RACKMETER depends on PPC_PMAC help This driver provides some support to control the front panel - blue LEDs "vu-meter" of the XServer macs. + blue LEDs "vu-meter" of the XServer macs. config SENSORS_AMS tristate "Apple Motion Sensor driver"
Signature · 1 line
1.9.1
PATCH 73/114 drivers: gpu: Kconfig: pedantic formatting
In reply to Enrico Weigelt, metux IT consultFormatting of Kconfig files doesn't look so pretty, so let the Great White Handkerchief come around and clean it up.
--- drivers/gpu/drm/Kconfig | 8 +++---- drivers/gpu/drm/amd/acp/Kconfig | 20 ++++++++--------- drivers/gpu/drm/amd/lib/Kconfig | 10 ++++----- drivers/gpu/drm/ast/Kconfig | 11 +++++---- drivers/gpu/drm/bridge/Kconfig | 8 +++---- drivers/gpu/drm/cirrus/Kconfig | 14 ++++++------ drivers/gpu/drm/hisilicon/kirin/Kconfig | 6 ++--- drivers/gpu/drm/i2c/Kconfig | 2 +- drivers/gpu/drm/i915/Kconfig | 12 +++++----- drivers/gpu/drm/mgag200/Kconfig | 11 +++++---- drivers/gpu/drm/nouveau/Kconfig | 2 +- drivers/gpu/drm/omapdrm/displays/Kconfig | 38 ++++++++++++++++---------------- drivers/gpu/drm/omapdrm/dss/Kconfig | 12 +++++----- drivers/gpu/drm/rockchip/Kconfig | 8 +++---- drivers/gpu/drm/sun4i/Kconfig | 16 +++++++------- drivers/gpu/drm/udl/Kconfig | 2 +- drivers/gpu/drm/vc4/Kconfig | 8 +++---- drivers/gpu/drm/virtio/Kconfig | 6 ++--- drivers/gpu/drm/vmwgfx/Kconfig | 5 ++--- drivers/gpu/vga/Kconfig | 2 +- 20 files changed, 99 insertions(+), 102 deletions(-)
drivers/gpu/drm/Kconfig +4 -4
@@ -189,8 +189,8 @@ config DRM_RADEON tristate "ATI Radeon" depends on DRM && PCI && MMU select FW_LOADER - select DRM_KMS_HELPER - select DRM_TTM + select DRM_KMS_HELPER + select DRM_TTM select POWER_SUPPLY select HWMON select BACKLIGHT_CLASS_DEVICE
@@ -209,9 +209,9 @@ config DRM_AMDGPU tristate "AMD GPU" depends on DRM && PCI && MMU select FW_LOADER - select DRM_KMS_HELPER + select DRM_KMS_HELPER select DRM_SCHED - select DRM_TTM + select DRM_TTM select POWER_SUPPLY select HWMON select BACKLIGHT_CLASS_DEVICE
drivers/gpu/drm/amd/acp/Kconfig +10 -10
@@ -1,15 +1,15 @@ menu "ACP (Audio CoProcessor) Configuration" config DRM_AMD_ACP - bool "Enable AMD Audio CoProcessor IP support" - depends on DRM_AMDGPU - select MFD_CORE - select PM_GENERIC_DOMAINS if PM - help - Choose this option to enable ACP IP support for AMD SOCs. - This adds the ACP (Audio CoProcessor) IP driver and wires - it up into the amdgpu driver. The ACP block provides the DMA - engine for the i2s-based ALSA driver. It is required for audio - on APUs which utilize an i2s codec. + bool "Enable AMD Audio CoProcessor IP support" + depends on DRM_AMDGPU + select MFD_CORE + select PM_GENERIC_DOMAINS if PM + help + Choose this option to enable ACP IP support for AMD SOCs. + This adds the ACP (Audio CoProcessor) IP driver and wires + it up into the amdgpu driver. The ACP block provides the DMA + engine for the i2s-based ALSA driver. It is required for audio + on APUs which utilize an i2s codec. endmenu
drivers/gpu/drm/amd/lib/Kconfig +5 -5
@@ -7,22 +7,22 @@ config CHASH tristate default DRM_AMDGPU help - Statically sized closed hash table implementation with low - memory and CPU overhead. + Statically sized closed hash table implementation with low + memory and CPU overhead. config CHASH_STATS bool "Closed hash table performance statistics" depends on CHASH default n help - Enable collection of performance statistics for closed hash tables. + Enable collection of performance statistics for closed hash tables. config CHASH_SELFTEST bool "Closed hash table self test" depends on CHASH default n help - Runs a selftest during module load. Several module parameters - are available to modify the behaviour of the test. + Runs a selftest during module load. Several module parameters + are available to modify the behaviour of the test. endmenu
drivers/gpu/drm/ast/Kconfig +5 -6
@@ -5,9 +5,8 @@ config DRM_AST select DRM_KMS_HELPER select DRM_TTM help - Say yes for experimental AST GPU driver. Do not enable - this driver without having a working -modesetting, - and a version of AST that knows to fail if KMS - is bound to the driver. These GPUs are commonly found - in server chipsets. - + Say yes for experimental AST GPU driver. Do not enable + this driver without having a working -modesetting, + and a version of AST that knows to fail if KMS + is bound to the driver. These GPUs are commonly found + in server chipsets.
drivers/gpu/drm/bridge/Kconfig +4 -4
@@ -58,10 +58,10 @@ config DRM_MEGACHIPS_STDPXXXX_GE_B850V3_FW select DRM_KMS_HELPER select DRM_PANEL ---help--- - This is a driver for the display bridges of - GE B850v3 that convert dual channel LVDS - to DP++. This is used with the i.MX6 imx-ldb - driver. You are likely to say N here. + This is a driver for the display bridges of + GE B850v3 that convert dual channel LVDS + to DP++. This is used with the i.MX6 imx-ldb + driver. You are likely to say N here. config DRM_NXP_PTN3460 tristate "NXP PTN3460 DP/LVDS bridge"
drivers/gpu/drm/cirrus/Kconfig +7 -7
@@ -4,15 +4,15 @@ config DRM_CIRRUS_QEMU select DRM_KMS_HELPER select DRM_TTM help - This is a KMS driver for emulated cirrus device in qemu. - It is *NOT* intended for real cirrus devices. This requires - the modesetting userspace X.org driver. + This is a KMS driver for emulated cirrus device in qemu. + It is *NOT* intended for real cirrus devices. This requires + the modesetting userspace X.org driver. - Cirrus is obsolete, the hardware was designed in the 90ies - and can't keep up with todays needs. More background: - https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/ + Cirrus is obsolete, the hardware was designed in the 90ies + and can't keep up with todays needs. More background: + https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/ - Better alternatives are: + Better alternatives are: - stdvga (DRM_BOCHS, qemu -vga std, default in qemu 2.2+) - qxl (DRM_QXL, qemu -vga qxl, works best with spice) - virtio (DRM_VIRTIO_GPU), qemu -vga virtio)
drivers/gpu/drm/hisilicon/kirin/Kconfig +3 -3
@@ -14,6 +14,6 @@ config HISI_KIRIN_DW_DSI depends on DRM_HISI_KIRIN select DRM_MIPI_DSI help - This selects support for HiSilicon Kirin SoC specific extensions for - the Synopsys DesignWare DSI driver. If you want to enable MIPI DSI on - hi6220 based SoC, you should selet this option. + This selects support for HiSilicon Kirin SoC specific extensions for + the Synopsys DesignWare DSI driver. If you want to enable MIPI DSI on + hi6220 based SoC, you should selet this option.
drivers/gpu/drm/i2c/Kconfig +1 -1
@@ -1,5 +1,5 @@ menu "I2C encoder or helper chips" - depends on DRM && DRM_KMS_HELPER && I2C + depends on DRM && DRM_KMS_HELPER && I2C config DRM_I2C_CH7006 tristate "Chrontel ch7006 TV encoder"
drivers/gpu/drm/i915/Kconfig +6 -6
@@ -67,7 +67,7 @@ config DRM_I915_CAPTURE_ERROR This option enables capturing the GPU state when a hang is detected. This information is vital for triaging hangs and assists in debugging. Please report any hang to - https://bugs.freedesktop.org/enter_bug.cgi?product=DRI + https://bugs.freedesktop.org/enter_bug.cgi?product=DRI for triaging. If in doubt, say "Y".
@@ -96,11 +96,11 @@ config DRM_I915_USERPTR If in doubt, say "Y". config DRM_I915_GVT - bool "Enable Intel GVT-g graphics virtualization host support" - depends on DRM_I915 - depends on 64BIT - default n - help + bool "Enable Intel GVT-g graphics virtualization host support" + depends on DRM_I915 + depends on 64BIT + default n + help Choose this option if you want to enable Intel GVT-g graphics virtualization technology host support with integrated graphics. With GVT-g, it's possible to have one integrated graphics
drivers/gpu/drm/mgag200/Kconfig +5 -6
@@ -4,9 +4,8 @@ config DRM_MGAG200 select DRM_KMS_HELPER select DRM_TTM help - This is a KMS driver for the MGA G200 server chips, it - does not support the original MGA G200 or any of the desktop - chips. It requires 0.3.0 of the modesetting userspace driver, - and a version of mga driver that will fail on KMS enabled - devices. - + This is a KMS driver for the MGA G200 server chips, it + does not support the original MGA G200 or any of the desktop + chips. It requires 0.3.0 of the modesetting userspace driver, + and a version of mga driver that will fail on KMS enabled + devices.
drivers/gpu/drm/nouveau/Kconfig +1 -1
@@ -1,7 +1,7 @@ config DRM_NOUVEAU tristate "Nouveau (NVIDIA) cards" depends on DRM && PCI && MMU - select FW_LOADER + select FW_LOADER select DRM_KMS_HELPER select DRM_TTM select BACKLIGHT_CLASS_DEVICE if DRM_NOUVEAU_BACKLIGHT
drivers/gpu/drm/omapdrm/displays/Kconfig +19 -19
@@ -7,29 +7,29 @@ config DRM_OMAP_ENCODER_OPA362 through a GPIO. config DRM_OMAP_ENCODER_TFP410 - tristate "TFP410 DPI to DVI Encoder" + tristate "TFP410 DPI to DVI Encoder" help Driver for TFP410 DPI to DVI encoder. config DRM_OMAP_ENCODER_TPD12S015 - tristate "TPD12S015 HDMI ESD protection and level shifter" + tristate "TPD12S015 HDMI ESD protection and level shifter" help Driver for TPD12S015, which offers HDMI ESD protection and level shifting. config DRM_OMAP_CONNECTOR_DVI - tristate "DVI Connector" + tristate "DVI Connector" depends on I2C help Driver for a generic DVI connector. config DRM_OMAP_CONNECTOR_HDMI - tristate "HDMI Connector" + tristate "HDMI Connector" help Driver for a generic HDMI connector. config DRM_OMAP_CONNECTOR_ANALOG_TV - tristate "Analog TV Connector" + tristate "Analog TV Connector" help Driver for a generic analog TV connector.
@@ -58,29 +58,29 @@ config DRM_OMAP_PANEL_LGPHILIPS_LB035Q02 LCD Panel used on the Gumstix Overo Palo35 config DRM_OMAP_PANEL_SHARP_LS037V7DW01 - tristate "Sharp LS037V7DW01 LCD Panel" - depends on BACKLIGHT_CLASS_DEVICE - help - LCD Panel used in TI's SDP3430 and EVM boards + tristate "Sharp LS037V7DW01 LCD Panel" + depends on BACKLIGHT_CLASS_DEVICE + help + LCD Panel used in TI's SDP3430 and EVM boards config DRM_OMAP_PANEL_TPO_TD028TTEC1 - tristate "TPO TD028TTEC1 LCD Panel" - depends on SPI - help - LCD panel used in Openmoko. + tristate "TPO TD028TTEC1 LCD Panel" + depends on SPI + help + LCD panel used in Openmoko. config DRM_OMAP_PANEL_TPO_TD043MTEA1 - tristate "TPO TD043MTEA1 LCD Panel" - depends on SPI - help - LCD Panel used in OMAP3 Pandora + tristate "TPO TD043MTEA1 LCD Panel" + depends on SPI + help + LCD Panel used in OMAP3 Pandora config DRM_OMAP_PANEL_NEC_NL8048HL11 tristate "NEC NL8048HL11 Panel" depends on SPI depends on BACKLIGHT_CLASS_DEVICE help - This NEC NL8048HL11 panel is TFT LCD used in the - Zoom2/3/3630 sdp boards. + This NEC NL8048HL11 panel is TFT LCD used in the + Zoom2/3/3630 sdp boards. endmenu
drivers/gpu/drm/omapdrm/dss/Kconfig +6 -6
@@ -5,12 +5,12 @@ config OMAP_DSS_BASE tristate menuconfig OMAP2_DSS - tristate "OMAP2+ Display Subsystem support" + tristate "OMAP2+ Display Subsystem support" select OMAP_DSS_BASE select VIDEOMODE_HELPERS select OMAP2_DSS_INIT select HDMI - help + help OMAP2+ Display Subsystem support. if OMAP2_DSS
@@ -51,7 +51,7 @@ config OMAP2_DSS_DPI config OMAP2_DSS_VENC bool "VENC support" - default y + default y help OMAP Video Encoder support for S-Video and composite TV-out.
@@ -60,7 +60,7 @@ config OMAP2_DSS_HDMI_COMMON config OMAP4_DSS_HDMI bool "HDMI support for OMAP4" - default y + default y select OMAP2_DSS_HDMI_COMMON help HDMI support for OMAP4 based SoCs.
@@ -84,7 +84,7 @@ config OMAP5_DSS_HDMI config OMAP2_DSS_SDI bool "SDI support" - default n + default n help SDI (Serial Display Interface) support.
@@ -93,7 +93,7 @@ config OMAP2_DSS_SDI config OMAP2_DSS_DSI bool "DSI support" - default n + default n help MIPI DSI (Display Serial Interface) support.
drivers/gpu/drm/rockchip/Kconfig +4 -4
@@ -27,17 +27,17 @@ config ROCKCHIP_ANALOGIX_DP on RK3288 or RK3399 based SoC, you should select this option. config ROCKCHIP_CDN_DP - bool "Rockchip cdn DP" + bool "Rockchip cdn DP" depends on EXTCON=y || (EXTCON=m && DRM_ROCKCHIP=m) - help + help This selects support for Rockchip SoC specific extensions for the cdn DP driver. If you want to enable Dp on RK3399 based SoC, you should select this option. config ROCKCHIP_DW_HDMI - bool "Rockchip specific extensions for Synopsys DW HDMI" - help + bool "Rockchip specific extensions for Synopsys DW HDMI" + help This selects support for Rockchip SoC specific extensions for the Synopsys DesignWare HDMI driver. If you want to enable HDMI on RK3288 or RK3399 based SoC, you should select
drivers/gpu/drm/sun4i/Kconfig +8 -8
@@ -16,18 +16,18 @@ config DRM_SUN4I if DRM_SUN4I config DRM_SUN4I_HDMI - tristate "Allwinner A10 HDMI Controller Support" - default DRM_SUN4I - help + tristate "Allwinner A10 HDMI Controller Support" + default DRM_SUN4I + help Choose this option if you have an Allwinner SoC with an HDMI controller. config DRM_SUN4I_HDMI_CEC - bool "Allwinner A10 HDMI CEC Support" - depends on DRM_SUN4I_HDMI - select CEC_CORE - select CEC_PIN - help + bool "Allwinner A10 HDMI CEC Support" + depends on DRM_SUN4I_HDMI + select CEC_CORE + select CEC_PIN + help Choose this option if you have an Allwinner SoC with an HDMI controller and want to use CEC.
drivers/gpu/drm/udl/Kconfig +1 -1
@@ -7,4 +7,4 @@ config DRM_UDL select DRM_KMS_HELPER help This is a KMS driver for the USB displaylink video adapters. - Say M/Y to add support for these devices via drm/kms interfaces. + Say M/Y to add support for these devices via drm/kms interfaces.
drivers/gpu/drm/vc4/Kconfig +4 -4
@@ -21,9 +21,9 @@ config DRM_VC4 our display setup. config DRM_VC4_HDMI_CEC - bool "Broadcom VC4 HDMI CEC Support" - depends on DRM_VC4 - select CEC_CORE - help + bool "Broadcom VC4 HDMI CEC Support" + depends on DRM_VC4 + select CEC_CORE + help Choose this option if you have a Broadcom VC4 GPU and want to use CEC.
drivers/gpu/drm/virtio/Kconfig +3 -3
@@ -4,7 +4,7 @@ config DRM_VIRTIO_GPU select DRM_KMS_HELPER select DRM_TTM help - This is the virtual GPU driver for virtio. It can be used with - QEMU based VMMs (like KVM or Xen). + This is the virtual GPU driver for virtio. It can be used with + QEMU based VMMs (like KVM or Xen). - If unsure say M. + If unsure say M.
drivers/gpu/drm/vmwgfx/Kconfig +2 -3
@@ -22,6 +22,5 @@ config DRM_VMWGFX_FBCON depends on DRM_VMWGFX && FB bool "Enable framebuffer console under vmwgfx by default" help - Choose this option if you are shipping a new vmwgfx - userspace driver that supports using the kernel driver. - + Choose this option if you are shipping a new vmwgfx + userspace driver that supports using the kernel driver.
drivers/gpu/vga/Kconfig +1 -1
@@ -26,6 +26,6 @@ config VGA_SWITCHEROO help Many laptops released in 2008/9/10 have two GPUs with a multiplexer to switch between them. This adds support for dynamic switching when - X isn't running and delayed switching until the next logoff. This + X isn't running and delayed switching until the next logoff. This feature is called hybrid graphics, ATI PowerXpress, and Nvidia HybridPower.
Signature · 1 line
1.9.1