Commit 3cb2fccc5f48a4d6269dfd00b4db570fca2a04d5
Committed by
Adrian Bunk
1 parent
5d3f083d8f
Exists in
master
and in
4 other branches
Fix misc Kconfig typos
Fix various Kconfig typos. Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com> Acked-by: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Showing 24 changed files with 34 additions and 34 deletions Side-by-side Diff
- arch/arm/mach-ixp4xx/Kconfig
- arch/arm/mach-lh7a40x/Kconfig
- arch/arm/mach-s3c2410/Kconfig
- arch/arm/mm/Kconfig
- arch/cris/arch-v10/Kconfig
- arch/cris/arch-v10/drivers/Kconfig
- arch/cris/arch-v32/drivers/Kconfig
- arch/m68knommu/Kconfig
- arch/mips/Kconfig
- arch/powerpc/Kconfig
- arch/powerpc/platforms/83xx/Kconfig
- arch/ppc/Kconfig
- arch/sh/Kconfig
- arch/sparc/Kconfig
- drivers/char/Kconfig
- drivers/media/video/Kconfig
- drivers/mtd/maps/Kconfig
- drivers/net/Kconfig
- drivers/net/phy/Kconfig
- drivers/pci/Kconfig
- drivers/spi/Kconfig
- drivers/usb/host/Kconfig
- fs/Kconfig
- sound/Kconfig
arch/arm/mach-ixp4xx/Kconfig
... | ... | @@ -133,7 +133,7 @@ |
133 | 133 | into the kernel and we can use the standard read[bwl]/write[bwl] |
134 | 134 | macros. This is the preferred method due to speed but it |
135 | 135 | limits the system to just 64MB of PCI memory. This can be |
136 | - problamatic if using video cards and other memory-heavy devices. | |
136 | + problematic if using video cards and other memory-heavy devices. | |
137 | 137 | |
138 | 138 | 2) If > 64MB of memory space is required, the IXP4xx can be |
139 | 139 | configured to use indirect registers to access PCI This allows |
arch/arm/mach-lh7a40x/Kconfig
... | ... | @@ -8,7 +8,7 @@ |
8 | 8 | help |
9 | 9 | Say Y here if you are using the Sharp KEV7A400 development |
10 | 10 | board. This hardware is discontinued, so I'd be very |
11 | - suprised if you wanted this option. | |
11 | + surprised if you wanted this option. | |
12 | 12 | |
13 | 13 | config MACH_LPD7A400 |
14 | 14 | bool "LPD7A400 Card Engine" |
arch/arm/mach-s3c2410/Kconfig
arch/arm/mm/Kconfig
... | ... | @@ -197,7 +197,7 @@ |
197 | 197 | select CPU_CP15_MPU |
198 | 198 | help |
199 | 199 | ARM940T is a member of the ARM9TDMI family of general- |
200 | - purpose microprocessors with MPU and seperate 4KB | |
200 | + purpose microprocessors with MPU and separate 4KB | |
201 | 201 | instruction and 4KB data cases, each with a 4-word line |
202 | 202 | length. |
203 | 203 |
arch/cris/arch-v10/Kconfig
... | ... | @@ -323,7 +323,7 @@ |
323 | 323 | depends on ETRAX_ARCH_V10 |
324 | 324 | default "95a6" |
325 | 325 | help |
326 | - Waitstates for SRAM, Flash and peripherials (not DRAM). 95f8 is a | |
326 | + Waitstates for SRAM, Flash and peripherals (not DRAM). 95f8 is a | |
327 | 327 | good choice for most Axis products... |
328 | 328 | |
329 | 329 | config ETRAX_DEF_R_BUS_CONFIG |
arch/cris/arch-v10/drivers/Kconfig
... | ... | @@ -839,7 +839,7 @@ |
839 | 839 | default "0" |
840 | 840 | help |
841 | 841 | This controls the initial value of the trickle charge register. |
842 | - 0 = disabled (use this if you are unsure or have a non rechargable battery) | |
842 | + 0 = disabled (use this if you are unsure or have a non rechargeable battery) | |
843 | 843 | Otherwise the following values can be OR:ed together to control the |
844 | 844 | charge current: |
845 | 845 | 1 = 2kohm, 2 = 4kohm, 3 = 4kohm |
arch/cris/arch-v32/drivers/Kconfig
... | ... | @@ -88,7 +88,7 @@ |
88 | 88 | help |
89 | 89 | Enables the DMA7 input channel for ser0 (ttyS0). |
90 | 90 | If you do not enable DMA, an interrupt for each character will be |
91 | - used when receiveing data. | |
91 | + used when receiving data. | |
92 | 92 | Normally you want to use DMA, unless you use the DMA channel for |
93 | 93 | something else. |
94 | 94 | |
... | ... | @@ -157,7 +157,7 @@ |
157 | 157 | help |
158 | 158 | Enables the DMA5 input channel for ser1 (ttyS1). |
159 | 159 | If you do not enable DMA, an interrupt for each character will be |
160 | - used when receiveing data. | |
160 | + used when receiving data. | |
161 | 161 | Normally you want this on, unless you use the DMA channel for |
162 | 162 | something else. |
163 | 163 | |
... | ... | @@ -228,7 +228,7 @@ |
228 | 228 | help |
229 | 229 | Enables the DMA3 input channel for ser2 (ttyS2). |
230 | 230 | If you do not enable DMA, an interrupt for each character will be |
231 | - used when receiveing data. | |
231 | + used when receiving data. | |
232 | 232 | Normally you want to use DMA, unless you use the DMA channel for |
233 | 233 | something else. |
234 | 234 | |
... | ... | @@ -297,7 +297,7 @@ |
297 | 297 | help |
298 | 298 | Enables the DMA9 input channel for ser3 (ttyS3). |
299 | 299 | If you do not enable DMA, an interrupt for each character will be |
300 | - used when receiveing data. | |
300 | + used when receiving data. | |
301 | 301 | Normally you want to use DMA, unless you use the DMA channel for |
302 | 302 | something else. |
303 | 303 |
arch/m68knommu/Kconfig
... | ... | @@ -565,7 +565,7 @@ |
565 | 565 | depends on ROM |
566 | 566 | help |
567 | 567 | This is almost always the same as the base of the ROM. Since on all |
568 | - 68000 type varients the vectors are at the base of the boot device | |
568 | + 68000 type variants the vectors are at the base of the boot device | |
569 | 569 | on system startup. |
570 | 570 | |
571 | 571 | config ROMVECSIZE |
... | ... | @@ -574,7 +574,7 @@ |
574 | 574 | depends on ROM |
575 | 575 | help |
576 | 576 | Define the size of the vector region in ROM. For most 68000 |
577 | - varients this would be 0x400 bytes in size. Set to 0 if you do | |
577 | + variants this would be 0x400 bytes in size. Set to 0 if you do | |
578 | 578 | not want a vector region at the start of the ROM. |
579 | 579 | |
580 | 580 | config ROMSTART |
arch/mips/Kconfig
... | ... | @@ -865,7 +865,7 @@ |
865 | 865 | bool |
866 | 866 | |
867 | 867 | # |
868 | -# Endianess selection. Suffiently obscure so many users don't know what to | |
868 | +# Endianess selection. Sufficiently obscure so many users don't know what to | |
869 | 869 | # answer,so we try hard to limit the available choices. Also the use of a |
870 | 870 | # choice statement should be more obvious to the user. |
871 | 871 | # |
... | ... | @@ -874,7 +874,7 @@ |
874 | 874 | help |
875 | 875 | Some MIPS machines can be configured for either little or big endian |
876 | 876 | byte order. These modes require different kernels and a different |
877 | - Linux distribution. In general there is one prefered byteorder for a | |
877 | + Linux distribution. In general there is one preferred byteorder for a | |
878 | 878 | particular system but some systems are just as commonly used in the |
879 | 879 | one or the other endianess. |
880 | 880 |
arch/powerpc/Kconfig
... | ... | @@ -425,7 +425,7 @@ |
425 | 425 | default n |
426 | 426 | help |
427 | 427 | This option enables support for the Maple 970FX Evaluation Board. |
428 | - For more informations, refer to <http://www.970eval.com> | |
428 | + For more information, refer to <http://www.970eval.com> | |
429 | 429 | |
430 | 430 | config PPC_PASEMI |
431 | 431 | depends on PPC_MULTIPLATFORM && PPC64 |
arch/powerpc/platforms/83xx/Kconfig
... | ... | @@ -21,7 +21,7 @@ |
21 | 21 | Be aware that PCI buses can only function when SYS board is plugged |
22 | 22 | into the PIB (Platform IO Board) board from Freescale which provide |
23 | 23 | 3 PCI slots. The PIBs PCI initialization is the bootloader's |
24 | - responsiblilty. | |
24 | + responsibility. | |
25 | 25 | |
26 | 26 | config MPC834x_ITX |
27 | 27 | bool "Freescale MPC834x ITX" |
... | ... | @@ -30,7 +30,7 @@ |
30 | 30 | This option enables support for the MPC 834x ITX evaluation board. |
31 | 31 | |
32 | 32 | Be aware that PCI initialization is the bootloader's |
33 | - responsiblilty. | |
33 | + responsibility. | |
34 | 34 | |
35 | 35 | config MPC8360E_PB |
36 | 36 | bool "Freescale MPC8360E PB" |
arch/ppc/Kconfig
... | ... | @@ -724,7 +724,7 @@ |
724 | 724 | Be aware that PCI buses can only function when SYS board is plugged |
725 | 725 | into the PIB (Platform IO Board) board from Freescale which provide |
726 | 726 | 3 PCI slots. The PIBs PCI initialization is the bootloader's |
727 | - responsiblilty. | |
727 | + responsibility. | |
728 | 728 | |
729 | 729 | config EV64360 |
730 | 730 | bool "Marvell-EV64360BP" |
arch/sh/Kconfig
arch/sparc/Kconfig
... | ... | @@ -212,8 +212,8 @@ |
212 | 212 | tristate "Sun4m LED driver" |
213 | 213 | help |
214 | 214 | This driver toggles the front-panel LED on sun4m systems |
215 | - in a user-specifyable manner. It's state can be probed | |
216 | - by reading /proc/led and it's blinking mode can be changed | |
215 | + in a user-specifiable manner. Its state can be probed | |
216 | + by reading /proc/led and its blinking mode can be changed | |
217 | 217 | via writes to /proc/led |
218 | 218 | |
219 | 219 | source "fs/Kconfig.binfmt" |
drivers/char/Kconfig
... | ... | @@ -994,7 +994,7 @@ |
994 | 994 | help |
995 | 995 | If you say Y here, you will have a miscdevice named "/dev/hpet/". Each |
996 | 996 | open selects one of the timers supported by the HPET. The timers are |
997 | - non-periodioc and/or periodic. | |
997 | + non-periodic and/or periodic. | |
998 | 998 | |
999 | 999 | config HPET_RTC_IRQ |
1000 | 1000 | bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC |
drivers/media/video/Kconfig
... | ... | @@ -24,7 +24,7 @@ |
24 | 24 | decode audio/video standards. This option will autoselect |
25 | 25 | all pertinent modules to each selected video module. |
26 | 26 | |
27 | - Unselect this only if you know exaclty what you are doing, since | |
27 | + Unselect this only if you know exactly what you are doing, since | |
28 | 28 | it may break support on some boards. |
29 | 29 | |
30 | 30 | In doubt, say Y. |
drivers/mtd/maps/Kconfig
drivers/net/Kconfig
... | ... | @@ -32,7 +32,7 @@ |
32 | 32 | tristate "Intermediate Functional Block support" |
33 | 33 | depends on NET_CLS_ACT |
34 | 34 | ---help--- |
35 | - This is an intermidiate driver that allows sharing of | |
35 | + This is an intermediate driver that allows sharing of | |
36 | 36 | resources. |
37 | 37 | To compile this driver as a module, choose M here: the module |
38 | 38 | will be called ifb. If you want to use more than one ifb |
... | ... | @@ -2136,7 +2136,7 @@ |
2136 | 2136 | This driver supports the original Yukon chipset. A cleaner driver is |
2137 | 2137 | also available (skge) which seems to work better than this one. |
2138 | 2138 | |
2139 | - This driver does not support the newer Yukon2 chipset. A seperate | |
2139 | + This driver does not support the newer Yukon2 chipset. A separate | |
2140 | 2140 | driver, sky2, is provided to support Yukon2-based adapters. |
2141 | 2141 | |
2142 | 2142 | The following adapters are supported by this driver: |
drivers/net/phy/Kconfig
... | ... | @@ -61,8 +61,8 @@ |
61 | 61 | depends on PHYLIB |
62 | 62 | ---help--- |
63 | 63 | Adds the driver to PHY layer to cover the boards that do not have any PHY bound, |
64 | - but with the ability to manipulate with speed/link in software. The relavant MII | |
65 | - speed/duplex parameters could be effectively handled in user-specified fuction. | |
64 | + but with the ability to manipulate the speed/link in software. The relevant MII | |
65 | + speed/duplex parameters could be effectively handled in a user-specified function. | |
66 | 66 | Currently tested with mpc866ads. |
67 | 67 | |
68 | 68 | config FIXED_MII_10_FDX |
drivers/pci/Kconfig
... | ... | @@ -27,7 +27,7 @@ |
27 | 27 | smaller speedup on single processor machines. |
28 | 28 | |
29 | 29 | But it can also cause lots of bad things to happen. A number |
30 | - of PCI drivers can not properly handle running in this way, | |
30 | + of PCI drivers cannot properly handle running in this way, | |
31 | 31 | some will just not work properly at all, while others might |
32 | 32 | decide to blow up power supplies with a huge load all at once, |
33 | 33 | so use this option at your own risk. |
drivers/spi/Kconfig
... | ... | @@ -16,7 +16,7 @@ |
16 | 16 | controller and a chipselect. Most SPI slaves don't support |
17 | 17 | dynamic device discovery; some are even write-only or read-only. |
18 | 18 | |
19 | - SPI is widely used by microcontollers to talk with sensors, | |
19 | + SPI is widely used by microcontrollers to talk with sensors, | |
20 | 20 | eeprom and flash memory, codecs and various other controller |
21 | 21 | chips, analog to digital (and d-to-a) converters, and more. |
22 | 22 | MMC and SD cards can be accessed using SPI protocol; and for |
drivers/usb/host/Kconfig
... | ... | @@ -153,7 +153,7 @@ |
153 | 153 | adapter will *NOT* work with PC cards that do not contain an OHCI |
154 | 154 | controller. |
155 | 155 | |
156 | - For those PC cards that contain multiple OHCI controllers only ther | |
156 | + For those PC cards that contain multiple OHCI controllers only the | |
157 | 157 | first one is used. |
158 | 158 | |
159 | 159 | The driver consists of two modules, the "ftdi-elan" module is a |
fs/Kconfig
... | ... | @@ -1145,7 +1145,7 @@ |
1145 | 1145 | help |
1146 | 1146 | The BeOS File System (BeFS) is the native file system of Be, Inc's |
1147 | 1147 | BeOS. Notable features include support for arbitrary attributes |
1148 | - on files and directories, and database-like indeces on selected | |
1148 | + on files and directories, and database-like indices on selected | |
1149 | 1149 | attributes. (Also note that this driver doesn't make those features |
1150 | 1150 | available at this time). It is a 64 bit filesystem, so it supports |
1151 | 1151 | extremely large volumes and files. |
sound/Kconfig
... | ... | @@ -64,11 +64,11 @@ |
64 | 64 | |
65 | 65 | source "sound/mips/Kconfig" |
66 | 66 | |
67 | -# the following will depenend on the order of config. | |
67 | +# the following will depend on the order of config. | |
68 | 68 | # here assuming USB is defined before ALSA |
69 | 69 | source "sound/usb/Kconfig" |
70 | 70 | |
71 | -# the following will depenend on the order of config. | |
71 | +# the following will depend on the order of config. | |
72 | 72 | # here assuming PCMCIA is defined before ALSA |
73 | 73 | source "sound/pcmcia/Kconfig" |
74 | 74 |