Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

trivial: Miscellaneous documentation typo fixes

Fix various typos in documentation txts.

Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
  • Loading branch information...
commit 19f594600110377ec4037fdf7fb93a25ec516212 1 parent 19af5cd
Matt LaPlante authored Jiri Kosina committed

Showing 60 changed files with 94 additions and 94 deletions. Show diff stats Hide diff stats

  1. +2 2 Documentation/DMA-API.txt
  2. +1 1  Documentation/RCU/rculist_nulls.txt
  3. +1 1  Documentation/SM501.txt
  4. +1 1  Documentation/block/deadline-iosched.txt
  5. +1 1  Documentation/braille-console.txt
  6. +1 1  Documentation/driver-model/devres.txt
  7. +4 4 Documentation/edac.txt
  8. +1 1  Documentation/fb/sh7760fb.txt
  9. +1 1  Documentation/filesystems/autofs4-mount-control.txt
  10. +1 1  Documentation/filesystems/caching/netfs-api.txt
  11. +3 3 Documentation/filesystems/ext4.txt
  12. +1 1  Documentation/filesystems/fiemap.txt
  13. +1 1  Documentation/filesystems/nfs-rdma.txt
  14. +2 2 Documentation/filesystems/proc.txt
  15. +1 1  Documentation/filesystems/sysfs-pci.txt
  16. +4 4 Documentation/filesystems/vfat.txt
  17. +1 1  Documentation/gpio.txt
  18. +2 2 Documentation/kdump/kdump.txt
  19. +2 2 Documentation/kernel-parameters.txt
  20. +1 1  Documentation/kobject.txt
  21. +1 1  Documentation/laptops/acer-wmi.txt
  22. +1 1  Documentation/laptops/sony-laptop.txt
  23. +1 1  Documentation/laptops/thinkpad-acpi.txt
  24. +1 1  Documentation/local_ops.txt
  25. +4 4 Documentation/memory-hotplug.txt
  26. +1 1  Documentation/mn10300/ABI.txt
  27. +6 6 Documentation/mtd/nand_ecc.txt
  28. +3 3 Documentation/networking/bonding.txt
  29. +1 1  Documentation/networking/can.txt
  30. +1 1  Documentation/networking/dm9000.txt
  31. +1 1  Documentation/networking/l2tp.txt
  32. +1 1  Documentation/networking/netdevices.txt
  33. +1 1  Documentation/networking/phonet.txt
  34. +1 1  Documentation/networking/regulatory.txt
  35. +1 1  Documentation/power/regulator/consumer.txt
  36. +1 1  Documentation/power/regulator/overview.txt
  37. +1 1  Documentation/power/s2ram.txt
  38. +1 1  Documentation/power/userland-swsusp.txt
  39. +2 2 Documentation/powerpc/booting-without-of.txt
  40. +1 1  Documentation/powerpc/dts-bindings/fsl/cpm_qe/cpm.txt
  41. +1 1  Documentation/powerpc/dts-bindings/fsl/msi-pic.txt
  42. +2 2 Documentation/powerpc/dts-bindings/fsl/pmc.txt
  43. +1 1  Documentation/powerpc/qe_firmware.txt
  44. +2 2 Documentation/s390/Debugging390.txt
  45. +1 1  Documentation/scheduler/sched-nice-design.txt
  46. +1 1  Documentation/scsi/aic79xx.txt
  47. +2 2 Documentation/scsi/ncr53c8xx.txt
  48. +1 1  Documentation/scsi/sym53c8xx_2.txt
  49. +1 1  Documentation/sound/alsa/ALSA-Configuration.txt
  50. +1 1  Documentation/sound/alsa/HD-Audio.txt
  51. +1 1  Documentation/sound/alsa/hda_codec.txt
  52. +2 2 Documentation/sysctl/vm.txt
  53. +1 1  Documentation/timers/hpet.txt
  54. +1 1  Documentation/timers/timer_stats.txt
  55. +4 4 Documentation/usb/WUSB-Design-overview.txt
  56. +2 2 Documentation/usb/anchors.txt
  57. +1 1  Documentation/video4linux/cx18.txt
  58. +3 3 drivers/message/fusion/lsi/mpi_history.txt
  59. +2 2 drivers/staging/go7007/go7007.txt
  60. +1 1  drivers/staging/panel/lcd-panel-cgram.txt
4 Documentation/DMA-API.txt
@@ -676,8 +676,8 @@ this directory the following files can currently be found:
676 676 dma-api/all_errors This file contains a numeric value. If this
677 677 value is not equal to zero the debugging code
678 678 will print a warning for every error it finds
679   - into the kernel log. Be carefull with this
680   - option. It can easily flood your logs.
  679 + into the kernel log. Be careful with this
  680 + option, as it can easily flood your logs.
681 681
682 682 dma-api/disabled This read-only file contains the character 'Y'
683 683 if the debugging code is disabled. This can
2  Documentation/RCU/rculist_nulls.txt
@@ -118,7 +118,7 @@ to another chain) checking the final 'nulls' value if
118 118 the lookup met the end of chain. If final 'nulls' value
119 119 is not the slot number, then we must restart the lookup at
120 120 the beginning. If the object was moved to the same chain,
121   -then the reader doesnt care : It might eventually
  121 +then the reader doesn't care : It might eventually
122 122 scan the list again without harm.
123 123
124 124
2  Documentation/SM501.txt
@@ -5,7 +5,7 @@ Copyright 2006, 2007 Simtec Electronics
5 5
6 6 The Silicon Motion SM501 multimedia companion chip is a multifunction device
7 7 which may provide numerous interfaces including USB host controller USB gadget,
8   -Asyncronous Serial ports, Audio functions and a dual display video interface.
  8 +asynchronous serial ports, audio functions, and a dual display video interface.
9 9 The device may be connected by PCI or local bus with varying functions enabled.
10 10
11 11 Core
2  Documentation/block/deadline-iosched.txt
@@ -58,7 +58,7 @@ same criteria as reads.
58 58 front_merges (bool)
59 59 ------------
60 60
61   -Sometimes it happens that a request enters the io scheduler that is contigious
  61 +Sometimes it happens that a request enters the io scheduler that is contiguous
62 62 with a request that is already on the queue. Either it fits in the back of that
63 63 request, or it fits at the front. That is called either a back merge candidate
64 64 or a front merge candidate. Due to the way files are typically laid out,
2  Documentation/braille-console.txt
@@ -27,7 +27,7 @@ parameter.
27 27
28 28 For simplicity, only one braille console can be enabled, other uses of
29 29 console=brl,... will be discarded. Also note that it does not interfere with
30   -the console selection mecanism described in serial-console.txt
  30 +the console selection mechanism described in serial-console.txt
31 31
32 32 For now, only the VisioBraille device is supported.
33 33
2  Documentation/driver-model/devres.txt
@@ -188,7 +188,7 @@ For example, you can do something like the following.
188 188
189 189 void my_midlayer_destroy_something()
190 190 {
191   - devres_release_group(dev, my_midlayer_create_soemthing);
  191 + devres_release_group(dev, my_midlayer_create_something);
192 192 }
193 193
194 194
8 Documentation/edac.txt
@@ -23,8 +23,8 @@ first time, it was renamed to 'EDAC'.
23 23 The bluesmoke project at sourceforge.net is now utilized as a 'staging area'
24 24 for EDAC development, before it is sent upstream to kernel.org
25 25
26   -At the bluesmoke/EDAC project site, is a series of quilt patches against
27   -recent kernels, stored in a SVN respository. For easier downloading, there
  26 +At the bluesmoke/EDAC project site is a series of quilt patches against
  27 +recent kernels, stored in a SVN repository. For easier downloading, there
28 28 is also a tarball snapshot available.
29 29
30 30 ============================================================================
@@ -73,9 +73,9 @@ the vendor should tie the parity status bits to 0 if they do not intend
73 73 to generate parity. Some vendors do not do this, and thus the parity bit
74 74 can "float" giving false positives.
75 75
76   -In the kernel there is a pci device attribute located in sysfs that is
  76 +In the kernel there is a PCI device attribute located in sysfs that is
77 77 checked by the EDAC PCI scanning code. If that attribute is set,
78   -PCI parity/error scannining is skipped for that device. The attribute
  78 +PCI parity/error scanning is skipped for that device. The attribute
79 79 is:
80 80
81 81 broken_parity_status
2  Documentation/fb/sh7760fb.txt
... ... @@ -1,7 +1,7 @@
1 1 SH7760/SH7763 integrated LCDC Framebuffer driver
2 2 ================================================
3 3
4   -0. Overwiew
  4 +0. Overview
5 5 -----------
6 6 The SH7760/SH7763 have an integrated LCD Display controller (LCDC) which
7 7 supports (in theory) resolutions ranging from 1x1 to 1024x1024,
2  Documentation/filesystems/autofs4-mount-control.txt
@@ -369,7 +369,7 @@ The call requires an initialized struct autofs_dev_ioctl. There are two
369 369 possible variations. Both use the path field set to the path of the mount
370 370 point to check and the size field adjusted appropriately. One uses the
371 371 ioctlfd field to identify a specific mount point to check while the other
372   -variation uses the path and optionaly arg1 set to an autofs mount type.
  372 +variation uses the path and optionally arg1 set to an autofs mount type.
373 373 The call returns 1 if this is a mount point and sets arg1 to the device
374 374 number of the mount and field arg2 to the relevant super block magic
375 375 number (described below) or 0 if it isn't a mountpoint. In both cases
2  Documentation/filesystems/caching/netfs-api.txt
@@ -184,7 +184,7 @@ This has the following fields:
184 184 have index children.
185 185
186 186 If this function is not supplied or if it returns NULL then the first
187   - cache in the parent's list will be chosed, or failing that, the first
  187 + cache in the parent's list will be chosen, or failing that, the first
188 188 cache in the master list.
189 189
190 190 (4) A function to retrieve an object's key from the netfs [mandatory].
6 Documentation/filesystems/ext4.txt
@@ -294,7 +294,7 @@ max_batch_time=usec Maximum amount of time ext4 should wait for
294 294 amount of time (on average) that it takes to
295 295 finish committing a transaction. Call this time
296 296 the "commit time". If the time that the
297   - transactoin has been running is less than the
  297 + transaction has been running is less than the
298 298 commit time, ext4 will try sleeping for the
299 299 commit time to see if other operations will join
300 300 the transaction. The commit time is capped by
@@ -328,7 +328,7 @@ noauto_da_alloc replacing existing files via patterns such as
328 328 journal commit, in the default data=ordered
329 329 mode, the data blocks of the new file are forced
330 330 to disk before the rename() operation is
331   - commited. This provides roughly the same level
  331 + committed. This provides roughly the same level
332 332 of guarantees as ext3, and avoids the
333 333 "zero-length" problem that can happen when a
334 334 system crashes before the delayed allocation
@@ -358,7 +358,7 @@ written to the journal first, and then to its final location.
358 358 In the event of a crash, the journal can be replayed, bringing both data and
359 359 metadata into a consistent state. This mode is the slowest except when data
360 360 needs to be read from and written to disk at the same time where it
361   -outperforms all others modes. Curently ext4 does not have delayed
  361 +outperforms all others modes. Currently ext4 does not have delayed
362 362 allocation support if this data journalling mode is selected.
363 363
364 364 References
2  Documentation/filesystems/fiemap.txt
@@ -204,7 +204,7 @@ fiemap_check_flags() helper:
204 204
205 205 int fiemap_check_flags(struct fiemap_extent_info *fieinfo, u32 fs_flags);
206 206
207   -The struct fieinfo should be passed in as recieved from ioctl_fiemap(). The
  207 +The struct fieinfo should be passed in as received from ioctl_fiemap(). The
208 208 set of fiemap flags which the fs understands should be passed via fs_flags. If
209 209 fiemap_check_flags finds invalid user flags, it will place the bad values in
210 210 fieinfo->fi_flags and return -EBADR. If the file system gets -EBADR, from
2  Documentation/filesystems/nfs-rdma.txt
@@ -100,7 +100,7 @@ Installation
100 100 $ sudo cp utils/mount/mount.nfs /sbin/mount.nfs
101 101
102 102 In this location, mount.nfs will be invoked automatically for NFS mounts
103   - by the system mount commmand.
  103 + by the system mount command.
104 104
105 105 NOTE: mount.nfs and therefore nfs-utils-1.1.2 or greater is only needed
106 106 on the NFS client machine. You do not need this specific version of
4 Documentation/filesystems/proc.txt
@@ -366,7 +366,7 @@ just those considered 'most important'. The new vectors are:
366 366 RES, CAL, TLB -- rescheduling, call and TLB flush interrupts are
367 367 sent from one CPU to another per the needs of the OS. Typically,
368 368 their statistics are used by kernel developers and interested users to
369   - determine the occurance of interrupt of the given type.
  369 + determine the occurrence of interrupts of the given type.
370 370
371 371 The above IRQ vectors are displayed only when relevent. For example,
372 372 the threshold vector does not exist on x86_64 platforms. Others are
@@ -551,7 +551,7 @@ Committed_AS: The amount of memory presently allocated on the system.
551 551 memory once that memory has been successfully allocated.
552 552 VmallocTotal: total size of vmalloc memory area
553 553 VmallocUsed: amount of vmalloc area which is used
554   -VmallocChunk: largest contigious block of vmalloc area which is free
  554 +VmallocChunk: largest contiguous block of vmalloc area which is free
555 555
556 556 ..............................................................................
557 557
2  Documentation/filesystems/sysfs-pci.txt
@@ -72,7 +72,7 @@ The 'rom' file is special in that it provides read-only access to the device's
72 72 ROM file, if available. It's disabled by default, however, so applications
73 73 should write the string "1" to the file to enable it before attempting a read
74 74 call, and disable it following the access by writing "0" to the file. Note
75   -that the device must be enabled for a rom read to return data succesfully.
  75 +that the device must be enabled for a rom read to return data successfully.
76 76 In the event a driver is not bound to the device, it can be enabled using the
77 77 'enable' file, documented above.
78 78
8 Documentation/filesystems/vfat.txt
@@ -124,10 +124,10 @@ sys_immutable -- If set, ATTR_SYS attribute on FAT is handled as
124 124 flush -- If set, the filesystem will try to flush to disk more
125 125 early than normal. Not set by default.
126 126
127   -rodir -- FAT has the ATTR_RO (read-only) attribute. But on Windows,
128   - the ATTR_RO of the directory will be just ignored actually,
129   - and is used by only applications as flag. E.g. it's setted
130   - for the customized folder.
  127 +rodir -- FAT has the ATTR_RO (read-only) attribute. On Windows,
  128 + the ATTR_RO of the directory will just be ignored,
  129 + and is used only by applications as a flag (e.g. it's set
  130 + for the customized folder).
131 131
132 132 If you want to use ATTR_RO as read-only flag even for
133 133 the directory, set this option.
2  Documentation/gpio.txt
@@ -458,7 +458,7 @@ debugfs interface, since it provides control over GPIO direction and
458 458 value instead of just showing a gpio state summary. Plus, it could be
459 459 present on production systems without debugging support.
460 460
461   -Given approprate hardware documentation for the system, userspace could
  461 +Given appropriate hardware documentation for the system, userspace could
462 462 know for example that GPIO #23 controls the write protect line used to
463 463 protect boot loader segments in flash memory. System upgrade procedures
464 464 may need to temporarily remove that protection, first importing a GPIO,
4 Documentation/kdump/kdump.txt
@@ -108,7 +108,7 @@ There are two possible methods of using Kdump.
108 108
109 109 2) Or use the system kernel binary itself as dump-capture kernel and there is
110 110 no need to build a separate dump-capture kernel. This is possible
111   - only with the architecutres which support a relocatable kernel. As
  111 + only with the architectures which support a relocatable kernel. As
112 112 of today, i386, x86_64, ppc64 and ia64 architectures support relocatable
113 113 kernel.
114 114
@@ -222,7 +222,7 @@ Dump-capture kernel config options (Arch Dependent, ia64)
222 222 ----------------------------------------------------------
223 223
224 224 - No specific options are required to create a dump-capture kernel
225   - for ia64, other than those specified in the arch idependent section
  225 + for ia64, other than those specified in the arch independent section
226 226 above. This means that it is possible to use the system kernel
227 227 as a dump-capture kernel if desired.
228 228
4 Documentation/kernel-parameters.txt
@@ -1076,7 +1076,7 @@ and is between 256 and 4096 characters. It is defined in the file
1076 1076
1077 1077 kgdboc= [HW] kgdb over consoles.
1078 1078 Requires a tty driver that supports console polling.
1079   - (only serial suported for now)
  1079 + (only serial supported for now)
1080 1080 Format: <serial_device>[,baud]
1081 1081
1082 1082 kmac= [MIPS] korina ethernet MAC address.
@@ -1405,7 +1405,7 @@ and is between 256 and 4096 characters. It is defined in the file
1405 1405 ('y', default) or cooked coordinates ('n')
1406 1406
1407 1407 mtrr_chunk_size=nn[KMG] [X86]
1408   - used for mtrr cleanup. It is largest continous chunk
  1408 + used for mtrr cleanup. It is largest continuous chunk
1409 1409 that could hold holes aka. UC entries.
1410 1410
1411 1411 mtrr_gran_size=nn[KMG] [X86]
2  Documentation/kobject.txt
@@ -132,7 +132,7 @@ kobject_name():
132 132 const char *kobject_name(const struct kobject * kobj);
133 133
134 134 There is a helper function to both initialize and add the kobject to the
135   -kernel at the same time, called supprisingly enough kobject_init_and_add():
  135 +kernel at the same time, called surprisingly enough kobject_init_and_add():
136 136
137 137 int kobject_init_and_add(struct kobject *kobj, struct kobj_type *ktype,
138 138 struct kobject *parent, const char *fmt, ...);
2  Documentation/laptops/acer-wmi.txt
@@ -40,7 +40,7 @@ NOTE: The Acer Aspire One is not supported hardware. It cannot work with
40 40 acer-wmi until Acer fix their ACPI-WMI implementation on them, so has been
41 41 blacklisted until that happens.
42 42
43   -Please see the website for the current list of known working hardare:
  43 +Please see the website for the current list of known working hardware:
44 44
45 45 http://code.google.com/p/aceracpi/wiki/SupportedHardware
46 46
2  Documentation/laptops/sony-laptop.txt
@@ -22,7 +22,7 @@ If your laptop model supports it, you will find sysfs files in the
22 22 /sys/class/backlight/sony/
23 23 directory. You will be able to query and set the current screen
24 24 brightness:
25   - brightness get/set screen brightness (an iteger
  25 + brightness get/set screen brightness (an integer
26 26 between 0 and 7)
27 27 actual_brightness reading from this file will query the HW
28 28 to get real brightness value
2  Documentation/laptops/thinkpad-acpi.txt
@@ -506,7 +506,7 @@ generate input device EV_KEY events.
506 506 In addition to the EV_KEY events, thinkpad-acpi may also issue EV_SW
507 507 events for switches:
508 508
509   -SW_RFKILL_ALL T60 and later hardare rfkill rocker switch
  509 +SW_RFKILL_ALL T60 and later hardware rfkill rocker switch
510 510 SW_TABLET_MODE Tablet ThinkPads HKEY events 0x5009 and 0x500A
511 511
512 512 Non hot-key ACPI HKEY event map:
2  Documentation/local_ops.txt
@@ -34,7 +34,7 @@ out of order wrt other memory writes by the owner CPU.
34 34
35 35 It can be done by slightly modifying the standard atomic operations : only
36 36 their UP variant must be kept. It typically means removing LOCK prefix (on
37   -i386 and x86_64) and any SMP sychronization barrier. If the architecture does
  37 +i386 and x86_64) and any SMP synchronization barrier. If the architecture does
38 38 not have a different behavior between SMP and UP, including asm-generic/local.h
39 39 in your architecture's local.h is sufficient.
40 40
8 Documentation/memory-hotplug.txt
@@ -73,13 +73,13 @@ this phase is triggered automatically. ACPI can notify this event. If not,
73 73 (see Section 4.).
74 74
75 75 Logical Memory Hotplug phase is to change memory state into
76   -avaiable/unavailable for users. Amount of memory from user's view is
  76 +available/unavailable for users. Amount of memory from user's view is
77 77 changed by this phase. The kernel makes all memory in it as free pages
78 78 when a memory range is available.
79 79
80 80 In this document, this phase is described as online/offline.
81 81
82   -Logical Memory Hotplug phase is triggred by write of sysfs file by system
  82 +Logical Memory Hotplug phase is triggered by write of sysfs file by system
83 83 administrator. For the hot-add case, it must be executed after Physical Hotplug
84 84 phase by hand.
85 85 (However, if you writes udev's hotplug scripts for memory hotplug, these
@@ -334,7 +334,7 @@ MEMORY_CANCEL_ONLINE
334 334 Generated if MEMORY_GOING_ONLINE fails.
335 335
336 336 MEMORY_ONLINE
337   - Generated when memory has succesfully brought online. The callback may
  337 + Generated when memory has successfully brought online. The callback may
338 338 allocate pages from the new memory.
339 339
340 340 MEMORY_GOING_OFFLINE
@@ -359,7 +359,7 @@ The third argument is passed by pointer of struct memory_notify.
359 359 struct memory_notify {
360 360 unsigned long start_pfn;
361 361 unsigned long nr_pages;
362   - int status_cahnge_nid;
  362 + int status_change_nid;
363 363 }
364 364
365 365 start_pfn is start_pfn of online/offline memory.
2  Documentation/mn10300/ABI.txt
@@ -26,7 +26,7 @@ registers and the stack. If the first argument is a 64-bit value, it will be
26 26 passed in D0:D1. If the first argument is not a 64-bit value, but the second
27 27 is, the second will be passed entirely on the stack and D1 will be unused.
28 28
29   -Arguments smaller than 32-bits are not coelesced within a register or a stack
  29 +Arguments smaller than 32-bits are not coalesced within a register or a stack
30 30 word. For example, two byte-sized arguments will always be passed in separate
31 31 registers or word-sized stack slots.
32 32
12 Documentation/mtd/nand_ecc.txt
@@ -50,7 +50,7 @@ byte 255: bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 rp1 rp3 rp5 ... rp15
50 50 cp5 cp5 cp5 cp5 cp4 cp4 cp4 cp4
51 51
52 52 This figure represents a sector of 256 bytes.
53   -cp is my abbreviaton for column parity, rp for row parity.
  53 +cp is my abbreviation for column parity, rp for row parity.
54 54
55 55 Let's start to explain column parity.
56 56 cp0 is the parity that belongs to all bit0, bit2, bit4, bit6.
@@ -560,7 +560,7 @@ Measuring this code again showed big gain. When executing the original
560 560 linux code 1 million times, this took about 1 second on my system.
561 561 (using time to measure the performance). After this iteration I was back
562 562 to 0.075 sec. Actually I had to decide to start measuring over 10
563   -million interations in order not to loose too much accuracy. This one
  563 +million iterations in order not to lose too much accuracy. This one
564 564 definitely seemed to be the jackpot!
565 565
566 566 There is a little bit more room for improvement though. There are three
@@ -571,8 +571,8 @@ loop; This eliminates 3 statements per loop. Of course after the loop we
571 571 need to correct by adding:
572 572 rp4 ^= rp4_6;
573 573 rp6 ^= rp4_6
574   -Furthermore there are 4 sequential assingments to rp8. This can be
575   -encoded slightly more efficient by saving tmppar before those 4 lines
  574 +Furthermore there are 4 sequential assignments to rp8. This can be
  575 +encoded slightly more efficiently by saving tmppar before those 4 lines
576 576 and later do rp8 = rp8 ^ tmppar ^ notrp8;
577 577 (where notrp8 is the value of rp8 before those 4 lines).
578 578 Again a use of the commutative property of xor.
@@ -622,7 +622,7 @@ Not a big change, but every penny counts :-)
622 622 Analysis 7
623 623 ==========
624 624
625   -Acutally this made things worse. Not very much, but I don't want to move
  625 +Actually this made things worse. Not very much, but I don't want to move
626 626 into the wrong direction. Maybe something to investigate later. Could
627 627 have to do with caching again.
628 628
@@ -642,7 +642,7 @@ Analysis 8
642 642 This makes things worse. Let's stick with attempt 6 and continue from there.
643 643 Although it seems that the code within the loop cannot be optimised
644 644 further there is still room to optimize the generation of the ecc codes.
645   -We can simply calcualate the total parity. If this is 0 then rp4 = rp5
  645 +We can simply calculate the total parity. If this is 0 then rp4 = rp5
646 646 etc. If the parity is 1, then rp4 = !rp5;
647 647 But if rp4 = rp5 we do not need rp5 etc. We can just write the even bits
648 648 in the result byte and then do something like
6 Documentation/networking/bonding.txt
@@ -221,7 +221,7 @@ ad_select
221 221
222 222 - Any slave's 802.3ad association state changes
223 223
224   - - The bond's adminstrative state changes to up
  224 + - The bond's administrative state changes to up
225 225
226 226 count or 2
227 227
@@ -369,7 +369,7 @@ fail_over_mac
369 369 When this policy is used in conjuction with the mii
370 370 monitor, devices which assert link up prior to being
371 371 able to actually transmit and receive are particularly
372   - susecptible to loss of the gratuitous ARP, and an
  372 + susceptible to loss of the gratuitous ARP, and an
373 373 appropriate updelay setting may be required.
374 374
375 375 follow or 2
@@ -1794,7 +1794,7 @@ target to query.
1794 1794 generally referred to as "trunk failover." This is a feature of the
1795 1795 switch that causes the link state of a particular switch port to be set
1796 1796 down (or up) when the state of another switch port goes down (or up).
1797   -It's purpose is to propogate link failures from logically "exterior" ports
  1797 +Its purpose is to propagate link failures from logically "exterior" ports
1798 1798 to the logically "interior" ports that bonding is able to monitor via
1799 1799 miimon. Availability and configuration for trunk failover varies by
1800 1800 switch, but this can be a viable alternative to the ARP monitor when using
2  Documentation/networking/can.txt
@@ -327,7 +327,7 @@ solution for a couple of reasons:
327 327 return 1;
328 328 }
329 329
330   - /* paraniod check ... */
  330 + /* paranoid check ... */
331 331 if (nbytes < sizeof(struct can_frame)) {
332 332 fprintf(stderr, "read: incomplete CAN frame\n");
333 333 return 1;
2  Documentation/networking/dm9000.txt
@@ -129,7 +129,7 @@ PHY Link state polling
129 129 ----------------------
130 130
131 131 The driver keeps track of the link state and informs the network core
132   -about link (carrier) availablilty. This is managed by several methods
  132 +about link (carrier) availability. This is managed by several methods
133 133 depending on the version of the chip and on which PHY is being used.
134 134
135 135 For the internal PHY, the original (and currently default) method is
2  Documentation/networking/l2tp.txt
@@ -158,7 +158,7 @@ Sample Userspace Code
158 158 }
159 159 return 0;
160 160
161   -Miscellanous
  161 +Miscellaneous
162 162 ============
163 163
164 164 The PPPoL2TP driver was developed as part of the OpenL2TP project by
2  Documentation/networking/netdevices.txt
@@ -74,7 +74,7 @@ dev->hard_start_xmit:
74 74 for this and return NETDEV_TX_LOCKED when the spin lock fails.
75 75 The locking there should also properly protect against
76 76 set_multicast_list. Note that the use of NETIF_F_LLTX is deprecated.
77   - Dont use it for new drivers.
  77 + Don't use it for new drivers.
78 78
79 79 Context: Process with BHs disabled or BH (timer),
80 80 will be called with interrupts disabled by netconsole.
2  Documentation/networking/phonet.txt
@@ -36,7 +36,7 @@ Phonet packets have a common header as follows:
36 36 On Linux, the link-layer header includes the pn_media byte (see below).
37 37 The next 7 bytes are part of the network-layer header.
38 38
39   -The device ID is split: the 6 higher-order bits consitute the device
  39 +The device ID is split: the 6 higher-order bits constitute the device
40 40 address, while the 2 lower-order bits are used for multiplexing, as are
41 41 the 8-bit object identifiers. As such, Phonet can be considered as a
42 42 network layer with 6 bits of address space and 10 bits for transport
2  Documentation/networking/regulatory.txt
@@ -89,7 +89,7 @@ added to this document when its support is enabled.
89 89 Device drivers who provide their own built regulatory domain
90 90 do not need a callback as the channels registered by them are
91 91 the only ones that will be allowed and therefore *additional*
92   -cannels cannot be enabled.
  92 +channels cannot be enabled.
93 93
94 94 Example code - drivers hinting an alpha2:
95 95 ------------------------------------------
2  Documentation/power/regulator/consumer.txt
@@ -178,5 +178,5 @@ Consumers can uregister interest by calling :-
178 178 int regulator_unregister_notifier(struct regulator *regulator,
179 179 struct notifier_block *nb);
180 180
181   -Regulators use the kernel notifier framework to send event to thier interested
  181 +Regulators use the kernel notifier framework to send event to their interested
182 182 consumers.
2  Documentation/power/regulator/overview.txt
@@ -119,7 +119,7 @@ Some terms used in this document:-
119 119 battery power, USB power)
120 120
121 121 Regulator Domains: is the new current limit within the
122   - regulator operating parameters for input/ouput voltage.
  122 + regulator operating parameters for input/output voltage.
123 123
124 124 If the regulator request passes all the constraint tests
125 125 then the new regulator value is applied.
2  Documentation/power/s2ram.txt
@@ -63,7 +63,7 @@ hardware during resume operations where a value can be set that will
63 63 survive a reboot.
64 64
65 65 Consequence is that after a resume (even if it is successful) your system
66   -clock will have a value corresponding to the magic mumber instead of the
  66 +clock will have a value corresponding to the magic number instead of the
67 67 correct date/time! It is therefore advisable to use a program like ntp-date
68 68 or rdate to reset the correct date/time from an external time source when
69 69 using this trace option.
2  Documentation/power/userland-swsusp.txt
@@ -109,7 +109,7 @@ unfreeze user space processes frozen by SNAPSHOT_UNFREEZE if they are
109 109 still frozen when the device is being closed).
110 110
111 111 Currently it is assumed that the userland utilities reading/writing the
112   -snapshot image from/to the kernel will use a swap parition, called the resume
  112 +snapshot image from/to the kernel will use a swap partition, called the resume
113 113 partition, or a swap file as storage space (if a swap file is used, the resume
114 114 partition is the partition that holds this file). However, this is not really
115 115 required, as they can use, for example, a special (blank) suspend partition or
4 Documentation/powerpc/booting-without-of.txt
@@ -1356,7 +1356,7 @@ platforms are moved over to use the flattened-device-tree model.
1356 1356 - phy-map : 1 cell, optional, bitmap of addresses to probe the PHY
1357 1357 for, used if phy-address is absent. bit 0x00000001 is
1358 1358 MDIO address 0.
1359   - For Axon it can be absent, thouugh my current driver
  1359 + For Axon it can be absent, though my current driver
1360 1360 doesn't handle phy-address yet so for now, keep
1361 1361 0x00ffffff in it.
1362 1362 - rx-fifo-size-gige : 1 cell, Rx fifo size in bytes for 1000 Mb/sec
@@ -1438,7 +1438,7 @@ platforms are moved over to use the flattened-device-tree model.
1438 1438
1439 1439 The Xilinx EDK toolchain ships with a set of IP cores (devices) for use
1440 1440 in Xilinx Spartan and Virtex FPGAs. The devices cover the whole range
1441   - of standard device types (network, serial, etc.) and miscellanious
  1441 + of standard device types (network, serial, etc.) and miscellaneous
1442 1442 devices (gpio, LCD, spi, etc). Also, since these devices are
1443 1443 implemented within the fpga fabric every instance of the device can be
1444 1444 synthesised with different options that change the behaviour.
2  Documentation/powerpc/dts-bindings/fsl/cpm_qe/cpm.txt
@@ -19,7 +19,7 @@ Example:
19 19 reg = <119c0 30>;
20 20 }
21 21
22   -* Properties common to mulitple CPM/QE devices
  22 +* Properties common to multiple CPM/QE devices
23 23
24 24 - fsl,cpm-command : This value is ORed with the opcode and command flag
25 25 to specify the device on which a CPM command operates.
2  Documentation/powerpc/dts-bindings/fsl/msi-pic.txt
... ... @@ -1,6 +1,6 @@
1 1 * Freescale MSI interrupt controller
2 2
3   -Reguired properities:
  3 +Required properties:
4 4 - compatible : compatible list, contains 2 entries,
5 5 first is "fsl,CHIP-msi", where CHIP is the processor(mpc8610, mpc8572,
6 6 etc.) and the second is "fsl,mpic-msi" or "fsl,ipic-msi" depending on
4 Documentation/powerpc/dts-bindings/fsl/pmc.txt
@@ -15,8 +15,8 @@ Properties:
15 15 compatible; all statements below that apply to "fsl,mpc8548-pmc" also
16 16 apply to "fsl,mpc8641d-pmc".
17 17
18   - Compatibility does not include bit assigments in SCCR/PMCDR/DEVDISR; these
19   - bit assigments are indicated via the sleep specifier in each device's
  18 + Compatibility does not include bit assignments in SCCR/PMCDR/DEVDISR; these
  19 + bit assignments are indicated via the sleep specifier in each device's
20 20 sleep property.
21 21
22 22 - reg: For devices compatible with "fsl,mpc8349-pmc", the first resource
2  Documentation/powerpc/qe_firmware.txt
@@ -225,7 +225,7 @@ For example, to match the 8323, revision 1.0:
225 225 soc.major = 1
226 226 soc.minor = 0
227 227
228   -'padding' is neccessary for structure alignment. This field ensures that the
  228 +'padding' is necessary for structure alignment. This field ensures that the
229 229 'extended_modes' field is aligned on a 64-bit boundary.
230 230
231 231 'extended_modes' is a bitfield that defines special functionality which has an
4 Documentation/s390/Debugging390.txt
@@ -1984,7 +1984,7 @@ break *$pc
1984 1984
1985 1985 break *0x400618
1986 1986
1987   -heres a really useful one for large programs
  1987 +Here's a really useful one for large programs
1988 1988 rbr
1989 1989 Set a breakpoint for all functions matching REGEXP
1990 1990 e.g.
@@ -2211,7 +2211,7 @@ Breakpoint 2 at 0x4d87a4: file top.c, line 2609.
2211 2211 #5 0x51692c in readline_internal () at readline.c:521
2212 2212 #6 0x5164fe in readline (prompt=0x7ffff810 "\177ÿøx\177ÿ÷Ø\177ÿøxÀ")
2213 2213 at readline.c:349
2214   -#7 0x4d7a8a in command_line_input (prrompt=0x564420 "(gdb) ", repeat=1,
  2214 +#7 0x4d7a8a in command_line_input (prompt=0x564420 "(gdb) ", repeat=1,
2215 2215 annotation_suffix=0x4d6b44 "prompt") at top.c:2091
2216 2216 #8 0x4d6cf0 in command_loop () at top.c:1345
2217 2217 #9 0x4e25bc in main (argc=1, argv=0x7ffffdf4) at main.c:635
2  Documentation/scheduler/sched-nice-design.txt
@@ -55,7 +55,7 @@ To sum it up: we always wanted to make nice levels more consistent, but
55 55 within the constraints of HZ and jiffies and their nasty design level
56 56 coupling to timeslices and granularity it was not really viable.
57 57
58   -The second (less frequent but still periodically occuring) complaint
  58 +The second (less frequent but still periodically occurring) complaint
59 59 about Linux's nice level support was its assymetry around the origo
60 60 (which you can see demonstrated in the picture above), or more
61 61 accurately: the fact that nice level behavior depended on the _absolute_
2  Documentation/scsi/aic79xx.txt
@@ -194,7 +194,7 @@ The following information is available in this file:
194 194 - Packetized SCSI Protocol at 160MB/s and 320MB/s
195 195 - Quick Arbitration Selection (QAS)
196 196 - Retained Training Information (Rev B. ASIC only)
197   - - Interrupt Coalessing
  197 + - Interrupt Coalescing
198 198 - Initiator Mode (target mode not currently
199 199 supported)
200 200 - Support for the PCI-X standard up to 133MHz
4 Documentation/scsi/ncr53c8xx.txt
@@ -206,7 +206,7 @@ of MOVE MEMORY instructions.
206 206 The 896 and the 895A allows handling of the phase mismatch context from
207 207 SCRIPTS (avoids the phase mismatch interrupt that stops the SCSI processor
208 208 until the C code has saved the context of the transfer).
209   -Implementing this without using LOAD/STORE instructions would be painfull
  209 +Implementing this without using LOAD/STORE instructions would be painful
210 210 and I didn't even want to try it.
211 211
212 212 The 896 chip supports 64 bit PCI transactions and addressing, while the
@@ -240,7 +240,7 @@ characteristics. This feature may also reduce average command latency.
240 240 In order to really gain advantage of this feature, devices must have
241 241 a reasonable cache size (No miracle is to be expected for a low-end
242 242 hard disk with 128 KB or less).
243   -Some kown SCSI devices do not properly support tagged command queuing.
  243 +Some known SCSI devices do not properly support tagged command queuing.
244 244 Generally, firmware revisions that fix this kind of problems are available
245 245 at respective vendor web/ftp sites.
246 246 All I can say is that the hard disks I use on my machines behave well with
2  Documentation/scsi/sym53c8xx_2.txt
@@ -206,7 +206,7 @@ characteristics. This feature may also reduce average command latency.
206 206 In order to really gain advantage of this feature, devices must have
207 207 a reasonable cache size (No miracle is to be expected for a low-end
208 208 hard disk with 128 KB or less).
209   -Some kown old SCSI devices do not properly support tagged command queuing.
  209 +Some known old SCSI devices do not properly support tagged command queuing.
210 210 Generally, firmware revisions that fix this kind of problems are available
211 211 at respective vendor web/ftp sites.
212 212 All I can say is that I never have had problem with tagged queuing using
2  Documentation/sound/alsa/ALSA-Configuration.txt
@@ -754,7 +754,7 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
754 754 single_cmd - Use single immediate commands to communicate with
755 755 codecs (for debugging only)
756 756 enable_msi - Enable Message Signaled Interrupt (MSI) (default = off)
757   - power_save - Automatic power-saving timtout (in second, 0 =
  757 + power_save - Automatic power-saving timeout (in second, 0 =
758 758 disable)
759 759 power_save_controller - Reset HD-audio controller in power-saving mode
760 760 (default = on)
2  Documentation/sound/alsa/HD-Audio.txt
@@ -16,7 +16,7 @@ methods for the HD-audio hardware.
16 16 The HD-audio component consists of two parts: the controller chip and
17 17 the codec chips on the HD-audio bus. Linux provides a single driver
18 18 for all controllers, snd-hda-intel. Although the driver name contains
19   -a word of a well-known harware vendor, it's not specific to it but for
  19 +a word of a well-known hardware vendor, it's not specific to it but for
20 20 all controller chips by other companies. Since the HD-audio
21 21 controllers are supposed to be compatible, the single snd-hda-driver
22 22 should work in most cases. But, not surprisingly, there are known
2  Documentation/sound/alsa/hda_codec.txt
@@ -114,7 +114,7 @@ For writing a sequence of verbs, use snd_hda_sequence_write().
114 114
115 115 There are variants of cached read/write, snd_hda_codec_write_cache(),
116 116 snd_hda_sequence_write_cache(). These are used for recording the
117   -register states for the power-mangement resume. When no PM is needed,
  117 +register states for the power-management resume. When no PM is needed,
118 118 these are equivalent with non-cached version.
119 119
120 120 To retrieve the number of sub nodes connected to the given node, use
4 Documentation/sysctl/vm.txt
@@ -358,7 +358,7 @@ nr_pdflush_threads
358 358 The current number of pdflush threads. This value is read-only.
359 359 The value changes according to the number of dirty pages in the system.
360 360
361   -When neccessary, additional pdflush threads are created, one per second, up to
  361 +When necessary, additional pdflush threads are created, one per second, up to
362 362 nr_pdflush_threads_max.
363 363
364 364 ==============================================================
@@ -565,7 +565,7 @@ swappiness
565 565
566 566 This control is used to define how aggressive the kernel will swap
567 567 memory pages. Higher values will increase agressiveness, lower values
568   -descrease the amount of swap.
  568 +decrease the amount of swap.
569 569
570 570 The default value is 60.
571 571
2  Documentation/timers/hpet.txt
@@ -7,7 +7,7 @@ by Intel and Microsoft which can be found at
7 7
8 8 Each HPET has one fixed-rate counter (at 10+ MHz, hence "High Precision")
9 9 and up to 32 comparators. Normally three or more comparators are provided,
10   -each of which can generate oneshot interupts and at least one of which has
  10 +each of which can generate oneshot interrupts and at least one of which has
11 11 additional hardware to support periodic interrupts. The comparators are
12 12 also called "timers", which can be misleading since usually timers are
13 13 independent of each other ... these share a counter, complicating resets.
2  Documentation/timers/timer_stats.txt
@@ -62,7 +62,7 @@ Timerstats sample period: 3.888770 s
62 62
63 63 The first column is the number of events, the second column the pid, the third
64 64 column is the name of the process. The forth column shows the function which
65   -initialized the timer and in parantheses the callback function which was
  65 +initialized the timer and in parenthesis the callback function which was
66 66 executed on expiry.
67 67
68 68 Thomas, Ingo
8 Documentation/usb/WUSB-Design-overview.txt
@@ -84,7 +84,7 @@ The different logical parts of this driver are:
84 84
85 85 *UWB*: the Ultra-Wide-Band stack -- manages the radio and
86 86 associated spectrum to allow for devices sharing it. Allows to
87   - control bandwidth assingment, beaconing, scanning, etc
  87 + control bandwidth assignment, beaconing, scanning, etc
88 88
89 89 *
90 90
@@ -184,7 +184,7 @@ and sends the replies and notifications back to the API
184 184 [/uwb_rc_neh_grok()/]. Notifications are handled to the UWB daemon, that
185 185 is chartered, among other things, to keep the tab of how the UWB radio
186 186 neighborhood looks, creating and destroying devices as they show up or
187   -dissapear.
  187 +disappear.
188 188
189 189 Command execution is very simple: a command block is sent and a event
190 190 block or reply is expected back. For sending/receiving command/events, a
@@ -333,7 +333,7 @@ read descriptors and move our data.
333 333
334 334 *Device life cycle and keep alives*
335 335
336   -Everytime there is a succesful transfer to/from a device, we update a
  336 +Every time there is a successful transfer to/from a device, we update a
337 337 per-device activity timestamp. If not, every now and then we check and
338 338 if the activity timestamp gets old, we ping the device by sending it a
339 339 Keep Alive IE; it responds with a /DN_Alive/ pong during the DNTS (this
@@ -411,7 +411,7 @@ context (wa_xfer) and submit it. When the xfer is done, our callback is
411 411 called and we assign the status bits and release the xfer resources.
412 412
413 413 In dequeue() we are basically cancelling/aborting the transfer. We issue
414   -a xfer abort request to the HC, cancell all the URBs we had submitted
  414 +a xfer abort request to the HC, cancel all the URBs we had submitted
415 415 and not yet done and when all that is done, the xfer callback will be
416 416 called--this will call the URB callback.
417 417
4 Documentation/usb/anchors.txt
@@ -27,7 +27,7 @@ Association and disassociation of URBs with anchors
27 27
28 28 An association of URBs to an anchor is made by an explicit
29 29 call to usb_anchor_urb(). The association is maintained until
30   -an URB is finished by (successfull) completion. Thus disassociation
  30 +an URB is finished by (successful) completion. Thus disassociation
31 31 is automatic. A function is provided to forcibly finish (kill)
32 32 all URBs associated with an anchor.
33 33 Furthermore, disassociation can be made with usb_unanchor_urb()
@@ -76,4 +76,4 @@ usb_get_from_anchor()
76 76 Returns the oldest anchored URB of an anchor. The URB is unanchored
77 77 and returned with a reference. As you may mix URBs to several
78 78 destinations in one anchor you have no guarantee the chronologically
79   -first submitted URB is returned.
  79 +first submitted URB is returned.
2  Documentation/video4linux/cx18.txt
@@ -11,7 +11,7 @@ encoder chip:
11 11 2) Some people have problems getting the i2c bus to work.
12 12 The symptom is that the eeprom cannot be read and the card is
13 13 unusable. This is probably fixed, but if you have problems
14   - then post to the video4linux or ivtv-users mailinglist.
  14 + then post to the video4linux or ivtv-users mailing list.
15 15
16 16 3) VBI (raw or sliced) has not yet been implemented.
17 17
6 drivers/message/fusion/lsi/mpi_history.txt
@@ -130,7 +130,7 @@ mpi_ioc.h
130 130 * 08-08-01 01.02.01 Original release for v1.2 work.
131 131 * New format for FWVersion and ProductId in
132 132 * MSG_IOC_FACTS_REPLY and MPI_FW_HEADER.
133   - * 08-31-01 01.02.02 Addded event MPI_EVENT_SCSI_DEVICE_STATUS_CHANGE and
  133 + * 08-31-01 01.02.02 Added event MPI_EVENT_SCSI_DEVICE_STATUS_CHANGE and
134 134 * related structure and defines.
135 135 * Added event MPI_EVENT_ON_BUS_TIMER_EXPIRED.
136 136 * Added MPI_IOCINIT_FLAGS_DISCARD_FW_IMAGE.
@@ -190,7 +190,7 @@ mpi_ioc.h
190 190 * 10-11-06 01.05.12 Added MPI_IOCFACTS_EXCEPT_METADATA_UNSUPPORTED.
191 191 * Added MaxInitiators field to PortFacts reply.
192 192 * Added SAS Device Status Change ReasonCode for
193   - * asynchronous notificaiton.
  193 + * asynchronous notification.
194 194 * Added MPI_EVENT_SAS_EXPANDER_STATUS_CHANGE and event
195 195 * data structure.
196 196 * Added new ImageType values for FWDownload and FWUpload
@@ -623,7 +623,7 @@ mpi_fc.h
623 623 * 11-02-00 01.01.01 Original release for post 1.0 work
624 624 * 12-04-00 01.01.02 Added messages for Common Transport Send and
625 625 * Primitive Send.
626   - * 01-09-01 01.01.03 Modifed some of the new flags to have an MPI prefix
  626 + * 01-09-01 01.01.03 Modified some of the new flags to have an MPI prefix
627 627 * and modified the FcPrimitiveSend flags.
628 628 * 01-25-01 01.01.04 Move InitiatorIndex in LinkServiceRsp reply to a larger
629 629 * field.
4 drivers/staging/go7007/go7007.txt
@@ -2,7 +2,7 @@ This is a driver for the WIS GO7007SB multi-format video encoder.
2 2
3 3 Pete Eberlein <pete@sensoray.com>
4 4
5   -The driver was orignally released under the GPL and is currently hosted at:
  5 +The driver was originally released under the GPL and is currently hosted at:
6 6 http://nikosapi.org/wiki/index.php/WIS_Go7007_Linux_driver
7 7 The go7007 firmware can be acquired from the package on the site above.
8 8
@@ -24,7 +24,7 @@ These should be used instead of the non-standard GO7007 ioctls described
24 24 below.
25 25
26 26
27   -The README files from the orignal package appear below:
  27 +The README files from the original package appears below:
28 28
29 29 ---------------------------------------------------------------------------
30 30 WIS GO7007SB Public Linux Driver
2  drivers/staging/panel/lcd-panel-cgram.txt
@@ -3,7 +3,7 @@ characters 0 to 7. The escape code to define a new character is
3 3 '\e[LG' followed by one digit from 0 to 7, representing the character
4 4 number, and up to 8 couples of hex digits terminated by a semi-colon
5 5 (';'). Each couple of digits represents a line, with 1-bits for each
6   -illuminated pixel with LSB on the right. Lines are numberred from the
  6 +illuminated pixel with LSB on the right. Lines are numbered from the
7 7 top of the character to the bottom. On a 5x7 matrix, only the 5 lower
8 8 bits of the 7 first bytes are used for each character. If the string
9 9 is incomplete, only complete lines will be redefined. Here are some

0 comments on commit 19f5946

Please sign in to comment.
Something went wrong with that request. Please try again.