Kbuild/doc: fix links to Documentation files

+1 -1

arch/arm/mach-ixp2000/Kconfig

··· 14 14 help 15 15 Say 'Y' here if you want your kernel to support the Radisys 16 16 ENP2611 PCI network processing card. For more information on 17 - this card, see <file:Documentation/arm/ENP2611>. 17 + this card, see <file:Documentation/arm/IXP2000>. 18 18 19 19 config ARCH_IXDP2400 20 20 bool "Support Intel IXDP2400"

+1 -1

arch/h8300/Kconfig

··· 1 1 # 2 2 # For a description of the syntax of this configuration file, 3 - # see Documentation/kbuild/config-language.txt. 3 + # see Documentation/kbuild/kconfig-language.txt. 4 4 # 5 5 6 6 mainmenu "uClinux/h8300 (w/o MMU) Kernel Configuration"

+1 -1

arch/s390/Kconfig

··· 513 513 default n 514 514 help 515 515 Select this option if you want to build an zfcpdump enabled kernel. 516 - Refer to "Documentation/s390/zfcpdump.txt" for more details on this. 516 + Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this. 517 517 518 518 endmenu 519 519

+1 -1

arch/sh64/Kconfig

··· 1 1 # 2 2 # For a description of the syntax of this configuration file, 3 - # see Documentation/kbuild/config-language.txt. 3 + # see Documentation/kbuild/kconfig-language.txt. 4 4 # 5 5 6 6 mainmenu "Linux/SH64 Kernel Configuration"

+1 -1

arch/xtensa/Kconfig

··· 1 1 # For a description of the syntax of this configuration file, 2 - # see Documentation/kbuild/config-language.txt. 2 + # see Documentation/kbuild/kconfig-language.txt. 3 3 4 4 mainmenu "Linux/Xtensa Kernel Configuration" 5 5

+4 -4

drivers/net/wireless/iwlwifi/Kconfig

··· 96 96 97 97 If you want to compile the driver as a module ( = code which can be 98 98 inserted in and remvoed from the running kernel whenever you want), 99 - say M here and read <file:Documentation/modules.txt>. The module 100 - will be called iwl4965.ko. 99 + say M here and read <file:Documentation/kbuild/modules.txt>. The 100 + module will be called iwl4965.ko. 101 101 102 102 config IWL3945 103 103 tristate "Intel PRO/Wireless 3945ABG/BG Network Connection" ··· 124 124 125 125 If you want to compile the driver as a module ( = code which can be 126 126 inserted in and remvoed from the running kernel whenever you want), 127 - say M here and read <file:Documentation/modules.txt>. The module 128 - will be called iwl3945.ko. 127 + say M here and read <file:Documentation/kbuild/modules.txt>. The 128 + module will be called iwl3945.ko.

+2 -2

drivers/scsi/Kconfig

··· 172 172 don't need this for those tiny 6-slot cdrom changers. Media 173 173 changers are listed as "Type: Medium Changer" in /proc/scsi/scsi. 174 174 If you have such hardware and want to use it with linux, say Y 175 - here. Check <file:Documentation/scsi-changer.txt> for details. 175 + here. Check <file:Documentation/scsi/scsi-changer.txt> for details. 176 176 177 177 If you want to compile this as a module ( = code which can be 178 178 inserted in and removed from the running kernel whenever you want), 179 179 say M here and read <file:Documentation/kbuild/modules.txt> and 180 - <file:Documentation/scsi.txt>. The module will be called ch.o. 180 + <file:Documentation/scsi/scsi.txt>. The module will be called ch.o. 181 181 If unsure, say N. 182 182 183 183

+2 -2

drivers/video/Kconfig

··· 1509 1509 1510 1510 WARNING: Do not use any application that uses the 3D engine 1511 1511 (namely glide) while using this driver. 1512 - Please read the <file:Documentation/fb/README-sstfb.txt> for supported 1512 + Please read the <file:Documentation/fb/sstfb.txt> for supported 1513 1513 options and other important info support. 1514 1514 1515 1515 config FB_VT8623 ··· 1807 1807 This driver is also available as a module ( = code which can be 1808 1808 inserted and removed from the running kernel whenever you want). The 1809 1809 module will be called sm501fb. If you want to compile it as a module, 1810 - say M here and read <file:Documentation/modules.txt>. 1810 + say M here and read <file:Documentation/kbuild/modules.txt>. 1811 1811 1812 1812 If unsure, say N. 1813 1813

+2 -1

drivers/w1/Kconfig

··· 17 17 bool "Userspace communication over connector" 18 18 default y 19 19 --- help --- 20 - This allows to communicate with userspace using connector [Documentation/connector]. 20 + This allows to communicate with userspace using connector. For more 21 + information see <file:Documentation/connector/connector.txt>. 21 22 There are three types of messages between w1 core and userspace: 22 23 1. Events. They are generated each time new master or slave device found 23 24 either due to automatic or requested search.

+2 -2

drivers/watchdog/Kconfig

··· 15 15 implementation entirely in software (which can sometimes fail to 16 16 reboot the machine) and a driver for hardware watchdog boards, which 17 17 are more robust and can also keep track of the temperature inside 18 - your computer. For details, read <file:Documentation/watchdog/watchdog.txt> 19 - in the kernel source. 18 + your computer. For details, read 19 + <file:Documentation/watchdog/watchdog-api.txt> in the kernel source. 20 20 21 21 The watchdog is usually used together with the watchdog daemon 22 22 which is available from

+3 -3

fs/Kconfig

··· 504 504 including multiple file events, one-shot support, and unmount 505 505 notification. 506 506 507 - For more information, see Documentation/filesystems/inotify.txt 507 + For more information, see <file:Documentation/filesystems/inotify.txt> 508 508 509 509 If unsure, say Y. 510 510 ··· 518 518 directories via a single open fd. Events are read from the file 519 519 descriptor, which is also select()- and poll()-able. 520 520 521 - For more information, see Documentation/filesystems/inotify.txt 521 + For more information, see <file:Documentation/filesystems/inotify.txt> 522 522 523 523 If unsure, say Y. 524 524 ··· 1089 1089 depends on EXPERIMENTAL && KEYS && CRYPTO && NET 1090 1090 help 1091 1091 Encrypted filesystem that operates on the VFS layer. See 1092 - <file:Documentation/ecryptfs.txt> to learn more about 1092 + <file:Documentation/filesystems/ecryptfs.txt> to learn more about 1093 1093 eCryptfs. Userspace components are required and can be 1094 1094 obtained from <http://ecryptfs.sf.net>. 1095 1095

+2 -2

net/ipv4/netfilter/Kconfig

··· 128 128 eg. UNICAST, LOCAL, BROADCAST, ... 129 129 130 130 If you want to compile it as a module, say M here and read 131 - <file:Documentation/modules.txt>. If unsure, say `N'. 131 + <file:Documentation/kbuild/modules.txt>. If unsure, say `N'. 132 132 133 133 # `filter', generic and specific targets 134 134 config IP_NF_FILTER ··· 371 371 and OUTPUT chains. 372 372 373 373 If you want to compile it as a module, say M here and read 374 - <file:Documentation/modules.txt>. If unsure, say `N'. 374 + <file:Documentation/kbuild/modules.txt>. If unsure, say `N'. 375 375 376 376 # ARP tables 377 377 config IP_NF_ARPTABLES

+1 -1

net/netfilter/Kconfig

··· 363 363 the tables, chains, rules. 364 364 365 365 If you want to compile it as a module, say M here and read 366 - <file:Documentation/modules.txt>. If unsure, say `N'. 366 + <file:Documentation/kbuild/modules.txt>. If unsure, say `N'. 367 367 368 368 config NETFILTER_XT_TARGET_SECMARK 369 369 tristate '"SECMARK" target support'