treewide: replace '---help---' in Kconfig files with 'help'
Since commit 84af7a6194
("checkpatch: kconfig: prefer 'help' over
'---help---'"), the number of '---help---' has been gradually
decreasing, but there are still more than 2400 instances.
This commit finishes the conversion. While I touched the lines,
I also fixed the indentation.
There are a variety of indentation styles found.
a) 4 spaces + '---help---'
b) 7 spaces + '---help---'
c) 8 spaces + '---help---'
d) 1 space + 1 tab + '---help---'
e) 1 tab + '---help---' (correct indentation)
f) 1 tab + 1 space + '---help---'
g) 1 tab + 2 spaces + '---help---'
In order to convert all of them to 1 tab + 'help', I ran the
following commend:
$ find . -name 'Kconfig*' | xargs sed -i 's/^[[:space:]]*---help---/\thelp/'
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
这个提交包含在:
@@ -3,7 +3,7 @@ menu "CAN Device Drivers"
|
||||
|
||||
config CAN_VCAN
|
||||
tristate "Virtual Local CAN Interface (vcan)"
|
||||
---help---
|
||||
help
|
||||
Similar to the network loopback devices, vcan offers a
|
||||
virtual local CAN interface.
|
||||
|
||||
@@ -12,7 +12,7 @@ config CAN_VCAN
|
||||
|
||||
config CAN_VXCAN
|
||||
tristate "Virtual CAN Tunnel (vxcan)"
|
||||
---help---
|
||||
help
|
||||
Similar to the virtual ethernet driver veth, vxcan implements a
|
||||
local CAN traffic tunnel between two virtual CAN network devices.
|
||||
When creating a vxcan, two vxcan devices are created as pair.
|
||||
@@ -31,7 +31,7 @@ config CAN_VXCAN
|
||||
config CAN_SLCAN
|
||||
tristate "Serial / USB serial CAN Adaptors (slcan)"
|
||||
depends on TTY
|
||||
---help---
|
||||
help
|
||||
CAN driver for several 'low cost' CAN interfaces that are attached
|
||||
via serial lines or via USB-to-serial adapters using the LAWICEL
|
||||
ASCII protocol. The driver implements the tty linediscipline N_SLCAN.
|
||||
@@ -51,7 +51,7 @@ config CAN_SLCAN
|
||||
config CAN_DEV
|
||||
tristate "Platform CAN drivers with Netlink support"
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Enables the common framework for platform CAN drivers with Netlink
|
||||
support. This is the standard library for CAN drivers.
|
||||
If unsure, say Y.
|
||||
@@ -61,7 +61,7 @@ if CAN_DEV
|
||||
config CAN_CALC_BITTIMING
|
||||
bool "CAN bit-timing calculation"
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
If enabled, CAN bit-timing parameters will be calculated for the
|
||||
bit-rate specified via Netlink argument "bitrate" when the device
|
||||
get started. This works fine for the most common CAN controllers
|
||||
@@ -81,7 +81,7 @@ config CAN_LEDS
|
||||
# fulfills your needs instead of fixing this driver.
|
||||
depends on BROKEN
|
||||
select LEDS_TRIGGERS
|
||||
---help---
|
||||
help
|
||||
This option adds two LED triggers for packet receive and transmit
|
||||
events on each supported CAN device.
|
||||
|
||||
@@ -91,20 +91,20 @@ config CAN_LEDS
|
||||
config CAN_AT91
|
||||
tristate "Atmel AT91 onchip CAN controller"
|
||||
depends on (ARCH_AT91 || COMPILE_TEST) && HAS_IOMEM
|
||||
---help---
|
||||
help
|
||||
This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
|
||||
and AT91SAM9X5 processors.
|
||||
|
||||
config CAN_FLEXCAN
|
||||
tristate "Support for Freescale FLEXCAN based chips"
|
||||
depends on OF && HAS_IOMEM
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to support for Freescale FlexCAN.
|
||||
|
||||
config CAN_GRCAN
|
||||
tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
|
||||
depends on OF && HAS_DMA
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN.
|
||||
Note that the driver supports little endian, even though little
|
||||
endian syntheses of the cores would need some modifications on
|
||||
@@ -113,7 +113,7 @@ config CAN_GRCAN
|
||||
config CAN_JANZ_ICAN3
|
||||
tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
|
||||
depends on MFD_JANZ_CMODIO
|
||||
---help---
|
||||
help
|
||||
Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
|
||||
connects to a MODULbus carrier board.
|
||||
|
||||
@@ -136,7 +136,7 @@ config CAN_KVASER_PCIEFD
|
||||
config CAN_SUN4I
|
||||
tristate "Allwinner A10 CAN controller"
|
||||
depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to use CAN controller found on Allwinner
|
||||
A10/A20 SoCs.
|
||||
|
||||
@@ -146,7 +146,7 @@ config CAN_SUN4I
|
||||
config CAN_TI_HECC
|
||||
depends on ARM
|
||||
tristate "TI High End CAN Controller"
|
||||
---help---
|
||||
help
|
||||
Driver for TI HECC (High End CAN Controller) module found on many
|
||||
TI devices. The device specifications are available from www.ti.com
|
||||
|
||||
@@ -154,14 +154,14 @@ config CAN_XILINXCAN
|
||||
tristate "Xilinx CAN"
|
||||
depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST
|
||||
depends on COMMON_CLK && HAS_IOMEM
|
||||
---help---
|
||||
help
|
||||
Xilinx CAN driver. This driver supports both soft AXI CAN IP and
|
||||
Zynq CANPS IP.
|
||||
|
||||
config PCH_CAN
|
||||
tristate "Intel EG20T PCH CAN controller"
|
||||
depends on PCI && (X86_32 || COMPILE_TEST)
|
||||
---help---
|
||||
help
|
||||
This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which
|
||||
is an IOH for x86 embedded processor (Intel Atom E6xx series).
|
||||
This driver can access CAN bus.
|
||||
@@ -182,7 +182,7 @@ endif
|
||||
|
||||
config CAN_DEBUG_DEVICES
|
||||
bool "CAN devices debugging messages"
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want the CAN device drivers to produce a bunch of
|
||||
debug messages to the system log. Select this if you are having
|
||||
a problem with CAN support and want to see more of what is going
|
||||
|
@@ -7,7 +7,7 @@ if CAN_C_CAN
|
||||
|
||||
config CAN_C_CAN_PLATFORM
|
||||
tristate "Generic Platform Bus based C_CAN/D_CAN driver"
|
||||
---help---
|
||||
help
|
||||
This driver adds support for the C_CAN/D_CAN chips connected
|
||||
to the "platform bus" (Linux abstraction for directly to the
|
||||
processor attached devices) which can be found on various
|
||||
@@ -18,7 +18,7 @@ config CAN_C_CAN_PLATFORM
|
||||
config CAN_C_CAN_PCI
|
||||
tristate "Generic PCI Bus based C_CAN/D_CAN driver"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
This driver adds support for the C_CAN/D_CAN chips connected
|
||||
to the PCI bus.
|
||||
endif
|
||||
|
@@ -7,14 +7,14 @@ if CAN_CC770
|
||||
|
||||
config CAN_CC770_ISA
|
||||
tristate "ISA Bus based legacy CC770 driver"
|
||||
---help---
|
||||
help
|
||||
This driver adds legacy support for CC770 and AN82527 chips
|
||||
connected to the ISA bus using I/O port, memory mapped or
|
||||
indirect access.
|
||||
|
||||
config CAN_CC770_PLATFORM
|
||||
tristate "Generic Platform Bus based CC770 driver"
|
||||
---help---
|
||||
help
|
||||
This driver adds support for the CC770 and AN82527 chips
|
||||
connected to the "platform bus" (Linux abstraction for directly
|
||||
to the processor attached devices).
|
||||
|
@@ -2,7 +2,7 @@
|
||||
config CAN_IFI_CANFD
|
||||
depends on HAS_IOMEM
|
||||
tristate "IFI CAN_FD IP"
|
||||
---help---
|
||||
help
|
||||
This driver adds support for the I/F/I CAN_FD soft IP block
|
||||
connected to the "platform bus" (Linux abstraction for directly
|
||||
to the processor attached devices). The CAN_FD is most often
|
||||
|
@@ -1,7 +1,7 @@
|
||||
# SPDX-License-Identifier: GPL-2.0-only
|
||||
config CAN_M_CAN
|
||||
tristate "Bosch M_CAN support"
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want support for Bosch M_CAN controller framework.
|
||||
This is common support for devices that embed the Bosch M_CAN IP.
|
||||
|
||||
@@ -9,7 +9,7 @@ config CAN_M_CAN_PLATFORM
|
||||
tristate "Bosch M_CAN support for io-mapped devices"
|
||||
depends on HAS_IOMEM
|
||||
depends on CAN_M_CAN
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want support for IO Mapped Bosch M_CAN controller.
|
||||
This support is for devices that have the Bosch M_CAN controller
|
||||
IP embedded into the device and the IP is IO Mapped to the processor.
|
||||
@@ -18,7 +18,7 @@ config CAN_M_CAN_TCAN4X5X
|
||||
depends on CAN_M_CAN
|
||||
depends on REGMAP_SPI
|
||||
tristate "TCAN4X5X M_CAN device"
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want support for Texas Instruments TCAN4x5x
|
||||
M_CAN controller. This device is a peripherial device that uses the
|
||||
SPI bus for communication.
|
||||
|
@@ -2,7 +2,7 @@
|
||||
config CAN_MSCAN
|
||||
depends on PPC
|
||||
tristate "Support for Freescale MSCAN based chips"
|
||||
---help---
|
||||
help
|
||||
The Motorola Scalable Controller Area Network (MSCAN) definition
|
||||
is based on the MSCAN12 definition which is the specific
|
||||
implementation of the Motorola Scalable CAN concept targeted for
|
||||
@@ -13,7 +13,7 @@ if CAN_MSCAN
|
||||
config CAN_MPC5XXX
|
||||
tristate "Freescale MPC5xxx onboard CAN controller"
|
||||
depends on (PPC_MPC52xx || PPC_MPC512x)
|
||||
---help---
|
||||
help
|
||||
If you say yes here you get support for Freescale's MPC5xxx
|
||||
onboard CAN controller. Currently, the MPC5200, MPC5200B and
|
||||
MPC5121 (Rev. 2 and later) are supported.
|
||||
|
@@ -2,7 +2,7 @@
|
||||
config CAN_PEAK_PCIEFD
|
||||
depends on PCI
|
||||
tristate "PEAK-System PCAN-PCIe FD cards"
|
||||
---help---
|
||||
help
|
||||
This driver adds support for the PEAK-System PCI Express FD
|
||||
CAN-FD cards family.
|
||||
These 1x or 2x CAN-FD channels cards offer CAN 2.0 a/b as well as
|
||||
|
@@ -2,7 +2,7 @@
|
||||
config CAN_RCAR
|
||||
tristate "Renesas R-Car CAN controller"
|
||||
depends on ARCH_RENESAS || ARM
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to use CAN controller found on Renesas R-Car
|
||||
SoCs.
|
||||
|
||||
@@ -12,7 +12,7 @@ config CAN_RCAR
|
||||
config CAN_RCAR_CANFD
|
||||
tristate "Renesas R-Car CAN FD controller"
|
||||
depends on ARCH_RENESAS || ARM
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to use CAN FD controller found on
|
||||
Renesas R-Car SoCs. The driver puts the controller in CAN FD only
|
||||
mode, which can interoperate with CAN2.0 nodes but does not support
|
||||
|
@@ -9,7 +9,7 @@ if CAN_SJA1000
|
||||
config CAN_EMS_PCI
|
||||
tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
This driver is for the one, two or four channel CPC-PCI,
|
||||
CPC-PCIe and CPC-104P cards from EMS Dr. Thomas Wuensche
|
||||
(http://www.ems-wuensche.de).
|
||||
@@ -17,7 +17,7 @@ config CAN_EMS_PCI
|
||||
config CAN_EMS_PCMCIA
|
||||
tristate "EMS CPC-CARD Card"
|
||||
depends on PCMCIA
|
||||
---help---
|
||||
help
|
||||
This driver is for the one or two channel CPC-CARD cards from
|
||||
EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de).
|
||||
|
||||
@@ -34,14 +34,14 @@ config CAN_F81601
|
||||
config CAN_KVASER_PCI
|
||||
tristate "Kvaser PCIcanx and Kvaser PCIcan PCI Cards"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
This driver is for the PCIcanx and PCIcan cards (1, 2 or
|
||||
4 channel) from Kvaser (http://www.kvaser.com).
|
||||
|
||||
config CAN_PEAK_PCI
|
||||
tristate "PEAK PCAN-PCI/PCIe/miniPCI Cards"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
This driver is for the PCAN-PCI/PCIe/miniPCI cards
|
||||
(1, 2, 3 or 4 channels) from PEAK-System Technik
|
||||
(http://www.peak-system.com).
|
||||
@@ -52,7 +52,7 @@ config CAN_PEAK_PCIEC
|
||||
select I2C
|
||||
select I2C_ALGOBIT
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to use a PCAN-ExpressCard from PEAK-System
|
||||
Technik. This will also automatically select I2C and I2C_ALGO
|
||||
configuration options.
|
||||
@@ -61,7 +61,7 @@ config CAN_PEAK_PCMCIA
|
||||
tristate "PEAK PCAN-PC Card"
|
||||
depends on PCMCIA
|
||||
depends on HAS_IOPORT_MAP
|
||||
---help---
|
||||
help
|
||||
This driver is for the PCAN-PC Card PCMCIA adapter (1 or 2 channels)
|
||||
from PEAK-System (http://www.peak-system.com). To compile this
|
||||
driver as a module, choose M here: the module will be called
|
||||
@@ -70,7 +70,7 @@ config CAN_PEAK_PCMCIA
|
||||
config CAN_PLX_PCI
|
||||
tristate "PLX90xx PCI-bridge based Cards"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
This driver is for CAN interface cards based on
|
||||
the PLX90xx PCI bridge.
|
||||
Driver supports now:
|
||||
@@ -87,13 +87,13 @@ config CAN_PLX_PCI
|
||||
|
||||
config CAN_SJA1000_ISA
|
||||
tristate "ISA Bus based legacy SJA1000 driver"
|
||||
---help---
|
||||
help
|
||||
This driver adds legacy support for SJA1000 chips connected to
|
||||
the ISA bus using I/O port, memory mapped or indirect access.
|
||||
|
||||
config CAN_SJA1000_PLATFORM
|
||||
tristate "Generic Platform Bus based SJA1000 driver"
|
||||
---help---
|
||||
help
|
||||
This driver adds support for the SJA1000 chips connected to
|
||||
the "platform bus" (Linux abstraction for directly to the
|
||||
processor attached devices). Which can be found on various
|
||||
|
@@ -2,7 +2,7 @@
|
||||
config CAN_SOFTING
|
||||
tristate "Softing Gmbh CAN generic support"
|
||||
depends on HAS_IOMEM
|
||||
---help---
|
||||
help
|
||||
Support for CAN cards from Softing Gmbh & some cards
|
||||
from Vector Gmbh.
|
||||
Softing Gmbh CAN cards come with 1 or 2 physical busses.
|
||||
@@ -20,7 +20,7 @@ config CAN_SOFTING_CS
|
||||
tristate "Softing Gmbh CAN pcmcia cards"
|
||||
depends on PCMCIA
|
||||
depends on CAN_SOFTING
|
||||
---help---
|
||||
help
|
||||
Support for PCMCIA cards from Softing Gmbh & some cards
|
||||
from Vector Gmbh.
|
||||
You need firmware for these, which you can get at
|
||||
|
@@ -5,13 +5,13 @@ menu "CAN SPI interfaces"
|
||||
config CAN_HI311X
|
||||
tristate "Holt HI311x SPI CAN controllers"
|
||||
depends on CAN_DEV && SPI && HAS_DMA
|
||||
---help---
|
||||
help
|
||||
Driver for the Holt HI311x SPI CAN controllers.
|
||||
|
||||
config CAN_MCP251X
|
||||
tristate "Microchip MCP251x and MCP25625 SPI CAN controllers"
|
||||
depends on HAS_DMA
|
||||
---help---
|
||||
help
|
||||
Driver for the Microchip MCP251x and MCP25625 SPI CAN
|
||||
controllers.
|
||||
|
||||
|
@@ -4,25 +4,25 @@ menu "CAN USB interfaces"
|
||||
|
||||
config CAN_8DEV_USB
|
||||
tristate "8 devices USB2CAN interface"
|
||||
---help---
|
||||
help
|
||||
This driver supports the USB2CAN interface
|
||||
from 8 devices (http://www.8devices.com).
|
||||
|
||||
config CAN_EMS_USB
|
||||
tristate "EMS CPC-USB/ARM7 CAN/USB interface"
|
||||
---help---
|
||||
help
|
||||
This driver is for the one channel CPC-USB/ARM7 CAN/USB interface
|
||||
from EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de).
|
||||
|
||||
config CAN_ESD_USB2
|
||||
tristate "ESD USB/2 CAN/USB interface"
|
||||
---help---
|
||||
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"
|
||||
---help---
|
||||
help
|
||||
This driver supports the Geschwister Schneider and bytewerk.org
|
||||
candleLight USB CAN interfaces USB/CAN devices
|
||||
If unsure choose N,
|
||||
@@ -31,7 +31,7 @@ config CAN_GS_USB
|
||||
|
||||
config CAN_KVASER_USB
|
||||
tristate "Kvaser CAN/USB interface"
|
||||
---help---
|
||||
help
|
||||
This driver adds support for Kvaser CAN/USB devices like Kvaser
|
||||
Leaf Light, Kvaser USBcan II and Kvaser Memorator Pro 5xHS.
|
||||
|
||||
@@ -82,13 +82,13 @@ config CAN_KVASER_USB
|
||||
|
||||
config CAN_MCBA_USB
|
||||
tristate "Microchip CAN BUS Analyzer interface"
|
||||
---help---
|
||||
help
|
||||
This driver supports the CAN BUS Analyzer interface
|
||||
from Microchip (http://www.microchip.com/development-tools/).
|
||||
|
||||
config CAN_PEAK_USB
|
||||
tristate "PEAK PCAN-USB/USB Pro interfaces for CAN 2.0b/CAN-FD"
|
||||
---help---
|
||||
help
|
||||
This driver supports the PEAK-System Technik USB adapters that enable
|
||||
access to the CAN bus, with repect to the CAN 2.0b and/or CAN-FD
|
||||
standards, that is:
|
||||
@@ -104,7 +104,7 @@ config CAN_PEAK_USB
|
||||
|
||||
config CAN_UCAN
|
||||
tristate "Theobroma Systems UCAN interface"
|
||||
---help---
|
||||
help
|
||||
This driver supports the Theobroma Systems
|
||||
UCAN USB-CAN interface.
|
||||
|
||||
|
在新工单中引用
屏蔽一个用户