Commit 095096038d637c477ef3c1b674612bcbc4d60c2d

Authored by Matt LaPlante
Committed by Adrian Bunk
1 parent c73a668c09

Fix several typos in drivers/

Signed-off-by: Adrian Bunk <bunk@stusta.de>

Showing 22 changed files with 32 additions and 32 deletions Side-by-side Diff

drivers/firmware/Kconfig
... ... @@ -64,7 +64,7 @@
64 64 help
65 65 Say m if you want to have the option of updating the BIOS for your
66 66 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
67   - supporting application to comunicate with the BIOS regarding the new
  67 + supporting application to communicate with the BIOS regarding the new
68 68 image for the image update to take effect.
69 69 See <file:Documentation/dell_rbu.txt> for more details on the driver.
70 70  
drivers/i2c/busses/Kconfig
... ... @@ -333,10 +333,10 @@
333 333  
334 334 This driver is a light version of i2c-parport. It doesn't depend
335 335 on the parport driver, and uses direct I/O access instead. This
336   - might be prefered on embedded systems where wasting memory for
  336 + might be preferred on embedded systems where wasting memory for
337 337 the clean but heavy parport handling is not an option. The
338 338 drawback is a reduced portability and the impossibility to
339   - dasiy-chain other parallel port devices.
  339 + daisy-chain other parallel port devices.
340 340  
341 341 Don't say Y here if you said Y or M to i2c-parport. Saying M to
342 342 both is possible but both modules should not be loaded at the same
drivers/ieee1394/Kconfig
... ... @@ -140,7 +140,7 @@
140 140 help
141 141 This builds sbp2 for use with non-OHCI host adapters which do not
142 142 support physical DMA or for when ohci1394 is run with phys_dma=0.
143   - Physical DMA is data movement without assistence of the drivers'
  143 + Physical DMA is data movement without assistance of the drivers'
144 144 interrupt handlers. This option includes the interrupt handlers
145 145 that are required in absence of this hardware feature.
146 146  
drivers/input/keyboard/Kconfig
... ... @@ -177,7 +177,7 @@
177 177 However, it has been thoroughly tested and is stable.
178 178  
179 179 If you want full HIL support including support for multiple
180   - keyboards, mices and tablets, you have to enable the
  180 + keyboards, mice, and tablets, you have to enable the
181 181 "HP System Device Controller i8042 Support" in the input/serio
182 182 submenu.
183 183  
drivers/input/serio/Kconfig
... ... @@ -115,9 +115,9 @@
115 115 depends on GSC && SERIO
116 116 default y
117 117 ---help---
118   - This option enables supports for the the "System Device
  118 + This option enables support for the "System Device
119 119 Controller", an i8042 carrying microcode to manage a
120   - few miscellanous devices on some Hewlett Packard systems.
  120 + few miscellaneous devices on some Hewlett Packard systems.
121 121 The SDC itself contains a 10ms resolution timer/clock capable
122 122 of delivering interrupts on a periodic and one-shot basis.
123 123 The SDC may also be connected to a battery-backed real-time
drivers/isdn/hardware/eicon/Kconfig
... ... @@ -47,7 +47,7 @@
47 47 tristate "DIVA Maint driver support"
48 48 depends on ISDN_DIVAS && m
49 49 help
50   - Enable Divas Maintainance driver.
  50 + Enable Divas Maintenance driver.
51 51  
52 52 endmenu
drivers/isdn/hisax/Kconfig
... ... @@ -321,7 +321,7 @@
321 321 help
322 322 This enables HiSax support for the HFC-S PCI 2BDS0 based cards.
323 323  
324   - For more informations see under
  324 + For more information see under
325 325 <file:Documentation/isdn/README.hfc-pci>.
326 326  
327 327 config HISAX_W6692
drivers/macintosh/Kconfig
... ... @@ -186,7 +186,7 @@
186 186 depends on I2C && I2C_POWERMAC && PPC_PMAC && !PPC_PMAC64
187 187 help
188 188 This driver provides some thermostat and fan control for the
189   - iBook G4, and the ATI based aluminium PowerBooks, allowing slighlty
  189 + iBook G4, and the ATI based aluminium PowerBooks, allowing slightly
190 190 better fan behaviour by default, and some manual control.
191 191  
192 192 config THERM_PM72
drivers/media/dvb/cinergyT2/Kconfig
... ... @@ -56,7 +56,7 @@
56 56 measurements.
57 57  
58 58 Please keep in mind that these updates cause traffic on the tuner
59   - control bus and thus may or may not affect receiption sensitivity.
  59 + control bus and thus may or may not affect reception sensitivity.
60 60  
61 61 The default value should be a safe choice for common applications.
62 62  
drivers/media/video/Kconfig
... ... @@ -351,7 +351,7 @@
351 351 help
352 352 Support for Radio Data System (RDS) decoder. This allows seeing
353 353 radio station identification transmitted using this standard.
354   - Currentlly, it works only with bt8x8 chips.
  354 + Currently, it works only with bt8x8 chips.
355 355  
356 356 To compile this driver as a module, choose M here: the
357 357 module will be called saa6588.
drivers/mtd/chips/Kconfig
... ... @@ -270,7 +270,7 @@
270 270 tristate "JEDEC device support"
271 271 depends on MTD && MTD_OBSOLETE_CHIPS && BROKEN
272 272 help
273   - Enable older older JEDEC flash interface devices for self
  273 + Enable older JEDEC flash interface devices for self
274 274 programming flash. It is commonly used in older AMD chips. It is
275 275 only called JEDEC because the JEDEC association
276 276 <http://www.jedec.org/> distributes the identification codes for the
drivers/mtd/nand/Kconfig
... ... @@ -21,7 +21,7 @@
21 21 NAND flash device internally checks only bits transitioning
22 22 from 1 to 0. There is a rare possibility that even though the
23 23 device thinks the write was successful, a bit could have been
24   - flipped accidentaly due to device wear or something else.
  24 + flipped accidentally due to device wear or something else.
25 25  
26 26 config MTD_NAND_ECC_SMC
27 27 bool "NAND ECC Smart Media byte order"
drivers/mtd/onenand/Kconfig
... ... @@ -21,7 +21,7 @@
21 21 OneNAND flash device internally checks only bits transitioning
22 22 from 1 to 0. There is a rare possibility that even though the
23 23 device thinks the write was successful, a bit could have been
24   - flipped accidentaly due to device wear or something else.
  24 + flipped accidentally due to device wear or something else.
25 25  
26 26 config MTD_ONENAND_GENERIC
27 27 tristate "OneNAND Flash device via platform device driver"
drivers/net/wireless/Kconfig
... ... @@ -301,7 +301,7 @@
301 301 tristate "Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)"
302 302 depends on NET_RADIO && (PPC_PMAC || PCI || PCMCIA)
303 303 ---help---
304   - A driver for 802.11b wireless cards based based on the "Hermes" or
  304 + A driver for 802.11b wireless cards based on the "Hermes" or
305 305 Intersil HFA384x (Prism 2) MAC controller. This includes the vast
306 306 majority of the PCMCIA 802.11b cards (which are nearly all rebadges)
307 307 - except for the Cisco/Aironet cards. Cards supported include the
drivers/rapidio/Kconfig
... ... @@ -15,5 +15,5 @@
15 15 default "30"
16 16 ---help---
17 17 Amount of time a discovery node waits for a host to complete
18   - enumeration beforing giving up.
  18 + enumeration before giving up.
drivers/scsi/Kconfig
... ... @@ -40,10 +40,10 @@
40 40 default y
41 41 ---help---
42 42 This option enables support for the various files in
43   - /proc/scsi. In Linux 2.6 this has been superceeded by
  43 + /proc/scsi. In Linux 2.6 this has been superseded by
44 44 files in sysfs but many legacy applications rely on this.
45 45  
46   - If unusure say Y.
  46 + If unsure say Y.
47 47  
48 48 comment "SCSI support type (disk, tape, CD-ROM)"
49 49 depends on SCSI
drivers/scsi/aic7xxx/Kconfig.aic79xx
... ... @@ -22,12 +22,12 @@
22 22 to be used for any device. The aic7xxx driver will automatically
23 23 vary this number based on device behavior. For devices with a
24 24 fixed maximum, the driver will eventually lock to this maximum
25   - and display a console message inidicating this value.
  25 + and display a console message indicating this value.
26 26  
27 27 Due to resource allocation issues in the Linux SCSI mid-layer, using
28 28 a high number of commands per device may result in memory allocation
29 29 failures when many devices are attached to the system. For this reason,
30   - the default is set to 32. Higher values may result in higer performance
  30 + the default is set to 32. Higher values may result in higher performance
31 31 on some devices. The upper bound is 253. 0 disables tagged queueing.
32 32  
33 33 Per device tag depth can be controlled via the kernel command line
drivers/scsi/aic7xxx/Kconfig.aic7xxx
... ... @@ -27,12 +27,12 @@
27 27 to be used for any device. The aic7xxx driver will automatically
28 28 vary this number based on device behavior. For devices with a
29 29 fixed maximum, the driver will eventually lock to this maximum
30   - and display a console message inidicating this value.
  30 + and display a console message indicating this value.
31 31  
32 32 Due to resource allocation issues in the Linux SCSI mid-layer, using
33 33 a high number of commands per device may result in memory allocation
34 34 failures when many devices are attached to the system. For this reason,
35   - the default is set to 32. Higher values may result in higer performance
  35 + the default is set to 32. Higher values may result in higher performance
36 36 on some devices. The upper bound is 253. 0 disables tagged queueing.
37 37  
38 38 Per device tag depth can be controlled via the kernel command line
drivers/serial/Kconfig
... ... @@ -121,7 +121,7 @@
121 121 default "4"
122 122 help
123 123 Set this to the maximum number of serial ports you want
124   - the kernel to register at boot time. This can be overriden
  124 + the kernel to register at boot time. This can be overridden
125 125 with the module parameter "nr_uarts", or boot-time parameter
126 126 8250.nr_uarts
127 127  
... ... @@ -205,7 +205,7 @@
205 205 depends on SERIAL_8250 != n && ISA && SERIAL_8250_MANY_PORTS
206 206 help
207 207 Say Y here if you have a Boca serial board. Please read the Boca
208   - mini-HOWTO, avaialble from <http://www.tldp.org/docs.html#howto>
  208 + mini-HOWTO, available from <http://www.tldp.org/docs.html#howto>
209 209  
210 210 To compile this driver as a module, choose M here: the module
211 211 will be called 8250_boca.
... ... @@ -667,7 +667,7 @@
667 667 depends on M68328 || M68EZ328 || M68VZ328
668 668 help
669 669 This driver supports the built-in serial port of the Motorola 68328
670   - (standard, EZ and VZ varities).
  670 + (standard, EZ and VZ varieties).
671 671  
672 672 config SERIAL_68328_RTS_CTS
673 673 bool "Support RTS/CTS on 68328 serial port"
drivers/usb/storage/Kconfig
... ... @@ -119,7 +119,7 @@
119 119 Say Y here to include additional code to support the Olympus MAUSB-10
120 120 and Fujifilm DPC-R1 USB Card reader/writer devices.
121 121  
122   - These devices are based on the Alauda chip and support support both
  122 + These devices are based on the Alauda chip and support both
123 123 XD and SmartMedia cards.
124 124  
125 125 config USB_STORAGE_ONETOUCH
drivers/video/Kconfig
... ... @@ -403,7 +403,7 @@
403 403 is based on the KS-108 lcd controller and is typically a matrix
404 404 of 2*n chips. This driver was tested with a 128x64 panel. This
405 405 driver supports it for use with x86 SBCs through a 16 bit GPIO
406   - interface (8 bit data, 8 bit control). If you anticpate using
  406 + interface (8 bit data, 8 bit control). If you anticipate using
407 407 this driver, say Y or M; otherwise say N. You must specify the
408 408 GPIO IO address to be used for setting control and data.
409 409  
... ... @@ -771,7 +771,7 @@
771 771 default n
772 772 help
773 773 Say Y here if you want the Riva driver to output all sorts
774   - of debugging informations to provide to the maintainer when
  774 + of debugging information to provide to the maintainer when
775 775 something goes wrong.
776 776  
777 777 config FB_RIVA_BACKLIGHT
... ... @@ -865,7 +865,7 @@
865 865 depends on FB_INTEL
866 866 ---help---
867 867 Say Y here if you want the Intel driver to output all sorts
868   - of debugging informations to provide to the maintainer when
  868 + of debugging information to provide to the maintainer when
869 869 something goes wrong.
870 870  
871 871 config FB_INTEL_I2C
... ... @@ -1062,7 +1062,7 @@
1062 1062 default n
1063 1063 help
1064 1064 Say Y here if you want the Radeon driver to output all sorts
1065   - of debugging informations to provide to the maintainer when
  1065 + of debugging information to provide to the maintainer when
1066 1066 something goes wrong.
1067 1067  
1068 1068 config FB_ATY128
... ... @@ -21,7 +21,7 @@
21 21 There are three types of messages between w1 core and userspace:
22 22 1. Events. They are generated each time new master or slave device found
23 23 either due to automatic or requested search.
24   - 2. Userspace commands. Includes read/write and search/alarm search comamnds.
  24 + 2. Userspace commands. Includes read/write and search/alarm search commands.
25 25 3. Replies to userspace commands.
26 26  
27 27 source drivers/w1/masters/Kconfig