Kbuild/doc: fix links to Documentation files
Fix links to files in Documentation/* in various Kconfig files Signed-off-by: Dirk Hohndel <hohndel@linux.intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Родитель
bdb76ef5a4
Коммит
e403149c92
|
@ -14,7 +14,7 @@ config ARCH_ENP2611
|
|||
help
|
||||
Say 'Y' here if you want your kernel to support the Radisys
|
||||
ENP2611 PCI network processing card. For more information on
|
||||
this card, see <file:Documentation/arm/ENP2611>.
|
||||
this card, see <file:Documentation/arm/IXP2000>.
|
||||
|
||||
config ARCH_IXDP2400
|
||||
bool "Support Intel IXDP2400"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
#
|
||||
# For a description of the syntax of this configuration file,
|
||||
# see Documentation/kbuild/config-language.txt.
|
||||
# see Documentation/kbuild/kconfig-language.txt.
|
||||
#
|
||||
|
||||
mainmenu "uClinux/h8300 (w/o MMU) Kernel Configuration"
|
||||
|
|
|
@ -513,7 +513,7 @@ config ZFCPDUMP
|
|||
default n
|
||||
help
|
||||
Select this option if you want to build an zfcpdump enabled kernel.
|
||||
Refer to "Documentation/s390/zfcpdump.txt" for more details on this.
|
||||
Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
|
||||
|
||||
endmenu
|
||||
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
#
|
||||
# For a description of the syntax of this configuration file,
|
||||
# see Documentation/kbuild/config-language.txt.
|
||||
# see Documentation/kbuild/kconfig-language.txt.
|
||||
#
|
||||
|
||||
mainmenu "Linux/SH64 Kernel Configuration"
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
# For a description of the syntax of this configuration file,
|
||||
# see Documentation/kbuild/config-language.txt.
|
||||
# see Documentation/kbuild/kconfig-language.txt.
|
||||
|
||||
mainmenu "Linux/Xtensa Kernel Configuration"
|
||||
|
||||
|
|
|
@ -96,8 +96,8 @@ config IWL4965
|
|||
|
||||
If you want to compile the driver as a module ( = code which can be
|
||||
inserted in and remvoed from the running kernel whenever you want),
|
||||
say M here and read <file:Documentation/modules.txt>. The module
|
||||
will be called iwl4965.ko.
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>. The
|
||||
module will be called iwl4965.ko.
|
||||
|
||||
config IWL3945
|
||||
tristate "Intel PRO/Wireless 3945ABG/BG Network Connection"
|
||||
|
@ -124,5 +124,5 @@ config IWL3945
|
|||
|
||||
If you want to compile the driver as a module ( = code which can be
|
||||
inserted in and remvoed from the running kernel whenever you want),
|
||||
say M here and read <file:Documentation/modules.txt>. The module
|
||||
will be called iwl3945.ko.
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>. The
|
||||
module will be called iwl3945.ko.
|
||||
|
|
|
@ -172,12 +172,12 @@ config CHR_DEV_SCH
|
|||
don't need this for those tiny 6-slot cdrom changers. Media
|
||||
changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
|
||||
If you have such hardware and want to use it with linux, say Y
|
||||
here. Check <file:Documentation/scsi-changer.txt> for details.
|
||||
here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
|
||||
|
||||
If you want to compile this 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> and
|
||||
<file:Documentation/scsi.txt>. The module will be called ch.o.
|
||||
<file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
|
||||
If unsure, say N.
|
||||
|
||||
|
||||
|
|
|
@ -1509,7 +1509,7 @@ config FB_VOODOO1
|
|||
|
||||
WARNING: Do not use any application that uses the 3D engine
|
||||
(namely glide) while using this driver.
|
||||
Please read the <file:Documentation/fb/README-sstfb.txt> for supported
|
||||
Please read the <file:Documentation/fb/sstfb.txt> for supported
|
||||
options and other important info support.
|
||||
|
||||
config FB_VT8623
|
||||
|
@ -1807,7 +1807,7 @@ config FB_SM501
|
|||
This driver is also available as a module ( = code which can be
|
||||
inserted and removed from the running kernel whenever you want). The
|
||||
module will be called sm501fb. If you want to compile it as a module,
|
||||
say M here and read <file:Documentation/modules.txt>.
|
||||
say M here and read <file:Documentation/kbuild/modules.txt>.
|
||||
|
||||
If unsure, say N.
|
||||
|
||||
|
|
|
@ -17,7 +17,8 @@ config W1_CON
|
|||
bool "Userspace communication over connector"
|
||||
default y
|
||||
--- help ---
|
||||
This allows to communicate with userspace using connector [Documentation/connector].
|
||||
This allows to communicate with userspace using connector. For more
|
||||
information see <file:Documentation/connector/connector.txt>.
|
||||
There are three types of messages between w1 core and userspace:
|
||||
1. Events. They are generated each time new master or slave device found
|
||||
either due to automatic or requested search.
|
||||
|
|
|
@ -15,8 +15,8 @@ menuconfig WATCHDOG
|
|||
implementation entirely in software (which can sometimes fail to
|
||||
reboot the machine) and a driver for hardware watchdog boards, which
|
||||
are more robust and can also keep track of the temperature inside
|
||||
your computer. For details, read <file:Documentation/watchdog/watchdog.txt>
|
||||
in the kernel source.
|
||||
your computer. For details, read
|
||||
<file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
|
||||
|
||||
The watchdog is usually used together with the watchdog daemon
|
||||
which is available from
|
||||
|
|
|
@ -504,7 +504,7 @@ config INOTIFY
|
|||
including multiple file events, one-shot support, and unmount
|
||||
notification.
|
||||
|
||||
For more information, see Documentation/filesystems/inotify.txt
|
||||
For more information, see <file:Documentation/filesystems/inotify.txt>
|
||||
|
||||
If unsure, say Y.
|
||||
|
||||
|
@ -518,7 +518,7 @@ config INOTIFY_USER
|
|||
directories via a single open fd. Events are read from the file
|
||||
descriptor, which is also select()- and poll()-able.
|
||||
|
||||
For more information, see Documentation/filesystems/inotify.txt
|
||||
For more information, see <file:Documentation/filesystems/inotify.txt>
|
||||
|
||||
If unsure, say Y.
|
||||
|
||||
|
@ -1089,7 +1089,7 @@ config ECRYPT_FS
|
|||
depends on EXPERIMENTAL && KEYS && CRYPTO && NET
|
||||
help
|
||||
Encrypted filesystem that operates on the VFS layer. See
|
||||
<file:Documentation/ecryptfs.txt> to learn more about
|
||||
<file:Documentation/filesystems/ecryptfs.txt> to learn more about
|
||||
eCryptfs. Userspace components are required and can be
|
||||
obtained from <http://ecryptfs.sf.net>.
|
||||
|
||||
|
|
|
@ -128,7 +128,7 @@ config IP_NF_MATCH_ADDRTYPE
|
|||
eg. UNICAST, LOCAL, BROADCAST, ...
|
||||
|
||||
If you want to compile it as a module, say M here and read
|
||||
<file:Documentation/modules.txt>. If unsure, say `N'.
|
||||
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
||||
|
||||
# `filter', generic and specific targets
|
||||
config IP_NF_FILTER
|
||||
|
@ -371,7 +371,7 @@ config IP_NF_RAW
|
|||
and OUTPUT chains.
|
||||
|
||||
If you want to compile it as a module, say M here and read
|
||||
<file:Documentation/modules.txt>. If unsure, say `N'.
|
||||
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
||||
|
||||
# ARP tables
|
||||
config IP_NF_ARPTABLES
|
||||
|
|
|
@ -363,7 +363,7 @@ config NETFILTER_XT_TARGET_TRACE
|
|||
the tables, chains, rules.
|
||||
|
||||
If you want to compile it as a module, say M here and read
|
||||
<file:Documentation/modules.txt>. If unsure, say `N'.
|
||||
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
|
||||
|
||||
config NETFILTER_XT_TARGET_SECMARK
|
||||
tristate '"SECMARK" target support'
|
||||
|
|
Загрузка…
Ссылка в новой задаче