trivial: Kconfig: .ko is normally not included in module names
.ko is normally not included in Kconfig help, make it consistent. Signed-off-by: Pavel Machek <pavel@ucw.cz> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
This commit is contained in:
Родитель
3226224039
Коммит
4737f0978d
|
@ -872,7 +872,7 @@ config BFIN_GPTIMERS
|
|||
are unsure, say N.
|
||||
|
||||
To compile this driver as a module, choose M here: the module
|
||||
will be called gptimers.ko.
|
||||
will be called gptimers.
|
||||
|
||||
choice
|
||||
prompt "Uncached DMA region"
|
||||
|
|
|
@ -112,7 +112,7 @@ config GDROM
|
|||
with up to 1 GB of data. This drive will also read standard CD ROM
|
||||
disks. Select this option to access any disks in your GD ROM drive.
|
||||
Most users will want to say "Y" here.
|
||||
You can also build this as a module which will be called gdrom.ko
|
||||
You can also build this as a module which will be called gdrom.
|
||||
|
||||
source "drivers/block/paride/Kconfig"
|
||||
|
||||
|
|
|
@ -692,7 +692,7 @@ config HVCS
|
|||
this driver.
|
||||
|
||||
To compile this driver as a module, choose M here: the
|
||||
module will be called hvcs.ko. Additionally, this module
|
||||
module will be called hvcs. Additionally, this module
|
||||
will depend on arch specific APIs exported from hvcserver.ko
|
||||
which will also be compiled when this driver is built as a
|
||||
module.
|
||||
|
|
|
@ -7,7 +7,7 @@ menuconfig CONNECTOR
|
|||
of the netlink socket protocol.
|
||||
|
||||
Connector support can also be built as a module. If so, the module
|
||||
will be called cn.ko.
|
||||
will be called cn.
|
||||
|
||||
if CONNECTOR
|
||||
|
||||
|
|
|
@ -34,7 +34,7 @@ config CRYPTO_DEV_PADLOCK_AES
|
|||
Available in VIA C3 and newer CPUs.
|
||||
|
||||
If unsure say M. The compiled module will be
|
||||
called padlock-aes.ko
|
||||
called padlock-aes.
|
||||
|
||||
config CRYPTO_DEV_PADLOCK_SHA
|
||||
tristate "PadLock driver for SHA1 and SHA256 algorithms"
|
||||
|
@ -47,7 +47,7 @@ config CRYPTO_DEV_PADLOCK_SHA
|
|||
Available in VIA C7 and newer processors.
|
||||
|
||||
If unsure say M. The compiled module will be
|
||||
called padlock-sha.ko
|
||||
called padlock-sha.
|
||||
|
||||
config CRYPTO_DEV_GEODE
|
||||
tristate "Support for the Geode LX AES engine"
|
||||
|
@ -79,7 +79,7 @@ config ZCRYPT_MONOLITHIC
|
|||
bool "Monolithic zcrypt module"
|
||||
depends on ZCRYPT="m"
|
||||
help
|
||||
Select this option if you want to have a single module z90crypt.ko
|
||||
Select this option if you want to have a single module z90crypt,
|
||||
that contains all parts of the crypto device driver (ap bus,
|
||||
request router and all the card drivers).
|
||||
|
||||
|
|
|
@ -46,7 +46,7 @@ menuconfig IDE
|
|||
SMART parameters from disk drives.
|
||||
|
||||
To compile this driver as a module, choose M here: the
|
||||
module will be called ide-core.ko.
|
||||
module will be called ide-core.
|
||||
|
||||
For further information, please read <file:Documentation/ide/ide.txt>.
|
||||
|
||||
|
|
|
@ -216,7 +216,7 @@ config DVB_USB_TTUSB2
|
|||
help
|
||||
Say Y here to support the Pinnacle 400e DVB-S USB2.0 receiver. The
|
||||
firmware protocol used by this module is similar to the one used by the
|
||||
old ttusb-driver - that's why the module is called dvb-usb-ttusb2.ko.
|
||||
old ttusb-driver - that's why the module is called dvb-usb-ttusb2.
|
||||
|
||||
config DVB_USB_DTT200U
|
||||
tristate "WideView WT-200U and WT-220U (pen) DVB-T USB2.0 support (Yakumo/Hama/Typhoon/Yuan)"
|
||||
|
|
|
@ -49,7 +49,7 @@ config MTD_MS02NV
|
|||
If you want to compile this driver as a module ( = code which can be
|
||||
inserted in and removed from the running kernel whenever you want),
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>.
|
||||
The module will be called ms02-nv.ko.
|
||||
The module will be called ms02-nv.
|
||||
|
||||
config MTD_DATAFLASH
|
||||
tristate "Support for AT45xxx DataFlash"
|
||||
|
|
|
@ -260,7 +260,7 @@ config MTD_NAND_BASLER_EXCITE
|
|||
help
|
||||
This enables the driver for the NAND flash device found on the
|
||||
Basler eXcite Smart Camera. If built as a module, the driver
|
||||
will be named "excite_nandflash.ko".
|
||||
will be named excite_nandflash.
|
||||
|
||||
config MTD_NAND_CAFE
|
||||
tristate "NAND support for OLPC CAFÉ chip"
|
||||
|
@ -282,7 +282,7 @@ config MTD_NAND_CS553X
|
|||
controller is enabled for NAND, and currently requires that
|
||||
the controller be in MMIO mode.
|
||||
|
||||
If you say "m", the module will be called "cs553x_nand.ko".
|
||||
If you say "m", the module will be called cs553x_nand.
|
||||
|
||||
config MTD_NAND_ATMEL
|
||||
tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
|
||||
|
|
|
@ -1880,7 +1880,7 @@ config FEC_MPC52xx
|
|||
---help---
|
||||
This option enables support for the MPC5200's on-chip
|
||||
Fast Ethernet Controller
|
||||
If compiled as module, it will be called 'fec_mpc52xx.ko'.
|
||||
If compiled as module, it will be called fec_mpc52xx.
|
||||
|
||||
config FEC_MPC52xx_MDIO
|
||||
bool "MPC52xx FEC MDIO bus driver"
|
||||
|
@ -1892,7 +1892,7 @@ config FEC_MPC52xx_MDIO
|
|||
(Motorola? industry standard).
|
||||
If your board uses an external PHY connected to FEC, enable this.
|
||||
If not sure, enable.
|
||||
If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
|
||||
If compiled as module, it will be called fec_mpc52xx_phy.
|
||||
|
||||
config NE_H8300
|
||||
tristate "NE2000 compatible support for H8/300"
|
||||
|
|
|
@ -310,7 +310,7 @@ config PRISM54
|
|||
If you want to compile the driver as a module ( = code which can be
|
||||
inserted in and removed from the running kernel whenever you want),
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>.
|
||||
The module will be called prism54.ko.
|
||||
The module will be called prism54.
|
||||
|
||||
config USB_ZD1201
|
||||
tristate "USB ZD1201 based Wireless device support"
|
||||
|
|
|
@ -29,7 +29,7 @@ config HOSTAP
|
|||
PLX/PCI/CS version of the driver to actually use the driver.
|
||||
|
||||
The driver can be compiled as a module and it will be called
|
||||
"hostap.ko".
|
||||
hostap.
|
||||
|
||||
config HOSTAP_FIRMWARE
|
||||
bool "Support downloading firmware images with Host AP driver"
|
||||
|
@ -68,7 +68,7 @@ config HOSTAP_PLX
|
|||
driver.
|
||||
|
||||
The driver can be compiled as a module and will be named
|
||||
"hostap_plx.ko".
|
||||
hostap_plx.
|
||||
|
||||
config HOSTAP_PCI
|
||||
tristate "Host AP driver for Prism2.5 PCI adaptors"
|
||||
|
@ -81,7 +81,7 @@ config HOSTAP_PCI
|
|||
driver.
|
||||
|
||||
The driver can be compiled as a module and will be named
|
||||
"hostap_pci.ko".
|
||||
hostap_pci.
|
||||
|
||||
config HOSTAP_CS
|
||||
tristate "Host AP driver for Prism2/2.5/3 PC Cards"
|
||||
|
@ -94,4 +94,4 @@ config HOSTAP_CS
|
|||
driver.
|
||||
|
||||
The driver can be compiled as a module and will be named
|
||||
"hostap_cs.ko".
|
||||
hostap_cs.
|
||||
|
|
|
@ -75,7 +75,7 @@ config IWLAGN
|
|||
If you want to compile the driver as a module ( = code which can be
|
||||
inserted in and removed from the running kernel whenever you want),
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>. The
|
||||
module will be called iwlagn.ko.
|
||||
module will be called iwlagn.
|
||||
|
||||
|
||||
config IWL4965
|
||||
|
@ -113,7 +113,7 @@ config IWL3945
|
|||
If you want to compile the driver as a module ( = code which can be
|
||||
inserted in and removed from the running kernel whenever you want),
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>. The
|
||||
module will be called iwl3945.ko.
|
||||
module will be called iwl3945.
|
||||
|
||||
config IWL3945_SPECTRUM_MEASUREMENT
|
||||
bool "Enable Spectrum Measurement in iwl3945 driver"
|
||||
|
|
|
@ -9,11 +9,11 @@ menuconfig RT2X00
|
|||
|
||||
When building one of the individual drivers, the rt2x00 library
|
||||
will also be created. That library (when the driver is built as
|
||||
a module) will be called "rt2x00lib.ko".
|
||||
a module) will be called rt2x00lib.
|
||||
|
||||
Additionally PCI and USB libraries will also be build depending
|
||||
on the types of drivers being selected, these libraries will be
|
||||
called "rt2x00pci.ko" and "rt2x00usb.ko".
|
||||
called rt2x00pci and rt2x00usb.
|
||||
|
||||
if RT2X00
|
||||
|
||||
|
@ -26,7 +26,7 @@ config RT2400PCI
|
|||
This adds support for rt2400 wireless chipset family.
|
||||
Supported chips: RT2460.
|
||||
|
||||
When compiled as a module, this driver will be called "rt2400pci.ko".
|
||||
When compiled as a module, this driver will be called rt2400pci.
|
||||
|
||||
config RT2500PCI
|
||||
tristate "Ralink rt2500 (PCI/PCMCIA) support"
|
||||
|
@ -37,7 +37,7 @@ config RT2500PCI
|
|||
This adds support for rt2500 wireless chipset family.
|
||||
Supported chips: RT2560.
|
||||
|
||||
When compiled as a module, this driver will be called "rt2500pci.ko".
|
||||
When compiled as a module, this driver will be called rt2500pci.
|
||||
|
||||
config RT61PCI
|
||||
tristate "Ralink rt2501/rt61 (PCI/PCMCIA) support"
|
||||
|
@ -51,7 +51,7 @@ config RT61PCI
|
|||
This adds support for rt2501 wireless chipset family.
|
||||
Supported chips: RT2561, RT2561S & RT2661.
|
||||
|
||||
When compiled as a module, this driver will be called "rt61pci.ko".
|
||||
When compiled as a module, this driver will be called rt61pci.
|
||||
|
||||
config RT2500USB
|
||||
tristate "Ralink rt2500 (USB) support"
|
||||
|
@ -62,7 +62,7 @@ config RT2500USB
|
|||
This adds support for rt2500 wireless chipset family.
|
||||
Supported chips: RT2571 & RT2572.
|
||||
|
||||
When compiled as a module, this driver will be called "rt2500usb.ko".
|
||||
When compiled as a module, this driver will be called rt2500usb.
|
||||
|
||||
config RT73USB
|
||||
tristate "Ralink rt2501/rt73 (USB) support"
|
||||
|
@ -75,7 +75,7 @@ config RT73USB
|
|||
This adds support for rt2501 wireless chipset family.
|
||||
Supported chips: RT2571W, RT2573 & RT2671.
|
||||
|
||||
When compiled as a module, this driver will be called "rt73usb.ko".
|
||||
When compiled as a module, this driver will be called rt73usb.
|
||||
|
||||
config RT2X00_LIB_PCI
|
||||
tristate
|
||||
|
|
|
@ -8,7 +8,7 @@ config LCS
|
|||
Select this option if you want to use LCS networking on IBM System z.
|
||||
This device driver supports Token Ring (IEEE 802.5),
|
||||
FDDI (IEEE 802.7) and Ethernet.
|
||||
To compile as a module, choose M. The module name is lcs.ko.
|
||||
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
|
||||
|
@ -21,7 +21,7 @@ config CTCM
|
|||
It also supports virtual CTCs when running under VM.
|
||||
This driver also supports channel-to-channel MPC SNA devices.
|
||||
MPC is an SNA protocol device used by Communication Server for Linux.
|
||||
To compile as a module, choose M. The module name is ctcm.ko.
|
||||
To compile as a module, choose M. The module name is ctcm.
|
||||
To compile into the kernel, choose Y.
|
||||
If you do not need any channel-to-channel connection, choose N.
|
||||
|
||||
|
@ -34,7 +34,7 @@ config NETIUCV
|
|||
link between VM guests. Using ifconfig a point-to-point connection
|
||||
can be established to the Linux on IBM System z
|
||||
running on the other VM guest. To compile as a module, choose M.
|
||||
The module name is netiucv.ko. If unsure, choose Y.
|
||||
The module name is netiucv. If unsure, choose Y.
|
||||
|
||||
config SMSGIUCV
|
||||
tristate "IUCV special message support (VM only)"
|
||||
|
@ -50,7 +50,7 @@ config CLAW
|
|||
This driver supports channel attached CLAW devices.
|
||||
CLAW is Common Link Access for Workstation. Common devices
|
||||
that use CLAW are RS/6000s, Cisco Routers (CIP) and 3172 devices.
|
||||
To compile as a module, choose M. The module name is claw.ko.
|
||||
To compile as a module, choose M. The module name is claw.
|
||||
To compile into the kernel, choose Y.
|
||||
|
||||
config QETH
|
||||
|
@ -65,14 +65,14 @@ config QETH
|
|||
<http://www.ibm.com/developerworks/linux/linux390>
|
||||
|
||||
To compile this driver as a module, choose M.
|
||||
The module name is qeth.ko.
|
||||
The module name is qeth.
|
||||
|
||||
config QETH_L2
|
||||
tristate "qeth layer 2 device support"
|
||||
depends on QETH
|
||||
help
|
||||
Select this option to be able to run qeth devices in layer 2 mode.
|
||||
To compile as a module, choose M. The module name is qeth_l2.ko.
|
||||
To compile as a module, choose M. The module name is qeth_l2.
|
||||
If unsure, choose y.
|
||||
|
||||
config QETH_L3
|
||||
|
@ -80,7 +80,7 @@ config QETH_L3
|
|||
depends on QETH
|
||||
help
|
||||
Select this option to be able to run qeth devices in layer 3 mode.
|
||||
To compile as a module choose M. The module name is qeth_l3.ko.
|
||||
To compile as a module choose M. The module name is qeth_l3.
|
||||
If unsure, choose Y.
|
||||
|
||||
config QETH_IPV6
|
||||
|
|
|
@ -861,7 +861,7 @@ config SERIAL_UARTLITE
|
|||
Say Y here if you want to use the Xilinx uartlite serial controller.
|
||||
|
||||
To compile this driver as a module, choose M here: the
|
||||
module will be called uartlite.ko.
|
||||
module will be called uartlite.
|
||||
|
||||
config SERIAL_UARTLITE_CONSOLE
|
||||
bool "Support for console on Xilinx uartlite serial port"
|
||||
|
|
|
@ -8,7 +8,7 @@ menuconfig W1
|
|||
If you want W1 support, you should say Y here.
|
||||
|
||||
This W1 support can also be built as a module. If so, the module
|
||||
will be called wire.ko.
|
||||
will be called wire.
|
||||
|
||||
if W1
|
||||
|
||||
|
|
|
@ -12,7 +12,7 @@ config W1_MASTER_MATROX
|
|||
using Matrox's G400 GPIO pins.
|
||||
|
||||
This support is also available as a module. If so, the module
|
||||
will be called matrox_w1.ko.
|
||||
will be called matrox_w1.
|
||||
|
||||
config W1_MASTER_DS2490
|
||||
tristate "DS2490 USB <-> W1 transport layer for 1-wire"
|
||||
|
@ -22,7 +22,7 @@ config W1_MASTER_DS2490
|
|||
for example DS9490*.
|
||||
|
||||
This support is also available as a module. If so, the module
|
||||
will be called ds2490.ko.
|
||||
will be called ds2490.
|
||||
|
||||
config W1_MASTER_DS2482
|
||||
tristate "Maxim DS2482 I2C to 1-Wire bridge"
|
||||
|
@ -56,7 +56,7 @@ config W1_MASTER_GPIO
|
|||
GPIO pins. This driver uses the GPIO API to control the wire.
|
||||
|
||||
This support is also available as a module. If so, the module
|
||||
will be called w1-gpio.ko.
|
||||
will be called w1-gpio.
|
||||
|
||||
config HDQ_MASTER_OMAP
|
||||
tristate "OMAP HDQ driver"
|
||||
|
|
|
@ -531,7 +531,7 @@ config SBC8360_WDT
|
|||
Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
|
||||
|
||||
To compile this driver as a module, choose M here: the
|
||||
module will be called sbc8360.ko.
|
||||
module will be called sbc8360.
|
||||
|
||||
Most people will say N.
|
||||
|
||||
|
|
|
@ -168,7 +168,7 @@ config IPV6_SIT
|
|||
into IPv4 packets. This is useful if you want to connect two IPv6
|
||||
networks over an IPv4-only path.
|
||||
|
||||
Saying M here will produce a module called sit.ko. If unsure, say Y.
|
||||
Saying M here will produce a module called sit. If unsure, say Y.
|
||||
|
||||
config IPV6_NDISC_NODETYPE
|
||||
bool
|
||||
|
|
|
@ -327,7 +327,7 @@ config NETFILTER_XT_TARGET_CONNMARK
|
|||
|
||||
If you want to compile it as a module, say M here and read
|
||||
<file:Documentation/kbuild/modules.txt>. The module will be called
|
||||
ipt_CONNMARK.ko. If unsure, say `N'.
|
||||
ipt_CONNMARK. If unsure, say `N'.
|
||||
|
||||
config NETFILTER_XT_TARGET_CONNSECMARK
|
||||
tristate '"CONNSECMARK" target support'
|
||||
|
@ -584,7 +584,7 @@ config NETFILTER_XT_MATCH_CONNMARK
|
|||
|
||||
If you want to compile it as a module, say M here and read
|
||||
<file:Documentation/kbuild/modules.txt>. The module will be called
|
||||
ipt_connmark.ko. If unsure, say `N'.
|
||||
ipt_connmark. If unsure, say `N'.
|
||||
|
||||
config NETFILTER_XT_MATCH_CONNTRACK
|
||||
tristate '"conntrack" connection tracking match support'
|
||||
|
|
Загрузка…
Ссылка в новой задаче