aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/RCU/whatisRCU.txt2
-rw-r--r--Documentation/block/biodoc.txt4
-rw-r--r--Documentation/cpu-freq/cpufreq-stats.txt8
-rw-r--r--Documentation/dvb/cards.txt2
-rw-r--r--Documentation/fb/sstfb.txt24
-rw-r--r--Documentation/filesystems/configfs/configfs.txt2
-rw-r--r--Documentation/filesystems/proc.txt4
-rw-r--r--Documentation/hrtimers.txt8
-rw-r--r--Documentation/input/yealink.txt2
-rw-r--r--Documentation/kbuild/kconfig-language.txt4
-rw-r--r--Documentation/networking/slicecom.txt4
-rw-r--r--Documentation/networking/smctr.txt2
-rw-r--r--Documentation/networking/tms380tr.txt2
-rw-r--r--Documentation/power/tricks.txt2
-rw-r--r--Documentation/powerpc/booting-without-of.txt6
-rw-r--r--Documentation/rocket.txt2
-rw-r--r--Documentation/s390/Debugging390.txt11
-rw-r--r--Documentation/s390/monreader.txt2
-rw-r--r--Documentation/scsi/aacraid.txt2
-rw-r--r--Documentation/scsi/aic79xx.txt2
-rw-r--r--Documentation/scsi/aic7xxx_old.txt2
-rw-r--r--Documentation/scsi/ibmmca.txt24
-rw-r--r--Documentation/scsi/ncr53c8xx.txt4
-rw-r--r--Documentation/scsi/st.txt2
-rw-r--r--Documentation/scsi/sym53c8xx_2.txt2
-rw-r--r--Documentation/sound/alsa/CMIPCI.txt4
-rw-r--r--Documentation/sound/alsa/MIXART.txt2
-rw-r--r--Documentation/sound/alsa/Procfile.txt4
-rw-r--r--Documentation/usb/URB.txt2
-rw-r--r--Documentation/usb/mtouchusb.txt2
30 files changed, 72 insertions, 71 deletions
diff --git a/Documentation/RCU/whatisRCU.txt b/Documentation/RCU/whatisRCU.txt
index 318df44259b3..f8092a891dd0 100644
--- a/Documentation/RCU/whatisRCU.txt
+++ b/Documentation/RCU/whatisRCU.txt
@@ -582,7 +582,7 @@ The rcu_read_lock() and rcu_read_unlock() primitive read-acquire
582and release a global reader-writer lock. The synchronize_rcu() 582and release a global reader-writer lock. The synchronize_rcu()
583primitive write-acquires this same lock, then immediately releases 583primitive write-acquires this same lock, then immediately releases
584it. This means that once synchronize_rcu() exits, all RCU read-side 584it. This means that once synchronize_rcu() exits, all RCU read-side
585critical sections that were in progress before synchonize_rcu() was 585critical sections that were in progress before synchronize_rcu() was
586called are guaranteed to have completed -- there is no way that 586called are guaranteed to have completed -- there is no way that
587synchronize_rcu() would have been able to write-acquire the lock 587synchronize_rcu() would have been able to write-acquire the lock
588otherwise. 588otherwise.
diff --git a/Documentation/block/biodoc.txt b/Documentation/block/biodoc.txt
index c41a3e1b4b39..e2f7dc6069c9 100644
--- a/Documentation/block/biodoc.txt
+++ b/Documentation/block/biodoc.txt
@@ -890,7 +890,7 @@ Aside:
890 890
891 Kvec i/o: 891 Kvec i/o:
892 892
893 Ben LaHaise's aio code uses a slighly different structure instead 893 Ben LaHaise's aio code uses a slightly different structure instead
894 of kiobufs, called a kvec_cb. This contains an array of <page, offset, len> 894 of kiobufs, called a kvec_cb. This contains an array of <page, offset, len>
895 tuples (very much like the networking code), together with a callback function 895 tuples (very much like the networking code), together with a callback function
896 and data pointer. This is embedded into a brw_cb structure when passed 896 and data pointer. This is embedded into a brw_cb structure when passed
@@ -988,7 +988,7 @@ elevator_exit_fn Allocate and free any elevator specific storage
988 for a queue. 988 for a queue.
989 989
9904.2 Request flows seen by I/O schedulers 9904.2 Request flows seen by I/O schedulers
991All requests seens by I/O schedulers strictly follow one of the following three 991All requests seen by I/O schedulers strictly follow one of the following three
992flows. 992flows.
993 993
994 set_req_fn -> 994 set_req_fn ->
diff --git a/Documentation/cpu-freq/cpufreq-stats.txt b/Documentation/cpu-freq/cpufreq-stats.txt
index 48bc2f1fff78..53d62c1e1c94 100644
--- a/Documentation/cpu-freq/cpufreq-stats.txt
+++ b/Documentation/cpu-freq/cpufreq-stats.txt
@@ -1,5 +1,5 @@
1 1
2 CPU frequency and voltage scaling statictics in the Linux(TM) kernel 2 CPU frequency and voltage scaling statistics in the Linux(TM) kernel
3 3
4 4
5 L i n u x c p u f r e q - s t a t s d r i v e r 5 L i n u x c p u f r e q - s t a t s d r i v e r
@@ -18,8 +18,8 @@ Contents
181. Introduction 181. Introduction
19 19
20cpufreq-stats is a driver that provices CPU frequency statistics for each CPU. 20cpufreq-stats is a driver that provices CPU frequency statistics for each CPU.
21This statistics is provided in /sysfs as a bunch of read_only interfaces. This 21These statistics are provided in /sysfs as a bunch of read_only interfaces. This
22interface (when configured) will appear in a seperate directory under cpufreq 22interface (when configured) will appear in a separate directory under cpufreq
23in /sysfs (<sysfs root>/devices/system/cpu/cpuX/cpufreq/stats/) for each CPU. 23in /sysfs (<sysfs root>/devices/system/cpu/cpuX/cpufreq/stats/) for each CPU.
24Various statistics will form read_only files under this directory. 24Various statistics will form read_only files under this directory.
25 25
@@ -115,7 +115,7 @@ basic statistics which includes time_in_state and total_trans.
115 115
116"CPU frequency translation statistics details" (CONFIG_CPU_FREQ_STAT_DETAILS) 116"CPU frequency translation statistics details" (CONFIG_CPU_FREQ_STAT_DETAILS)
117provides fine grained cpufreq stats by trans_table. The reason for having a 117provides fine grained cpufreq stats by trans_table. The reason for having a
118seperate config option for trans_table is: 118separate config option for trans_table is:
119- trans_table goes against the traditional /sysfs rule of one value per 119- trans_table goes against the traditional /sysfs rule of one value per
120 interface. It provides a whole bunch of value in a 2 dimensional matrix 120 interface. It provides a whole bunch of value in a 2 dimensional matrix
121 form. 121 form.
diff --git a/Documentation/dvb/cards.txt b/Documentation/dvb/cards.txt
index 9e10092440e1..ca58e339d85f 100644
--- a/Documentation/dvb/cards.txt
+++ b/Documentation/dvb/cards.txt
@@ -5,7 +5,7 @@ Hardware supported by the linuxtv.org DVB drivers
5 frontends (i.e. tuner / demodulator units) used, usually without 5 frontends (i.e. tuner / demodulator units) used, usually without
6 changing the product name, revision number or specs. Some cards 6 changing the product name, revision number or specs. Some cards
7 are also available in versions with different frontends for 7 are also available in versions with different frontends for
8 DVB-S/DVB-C/DVB-T. Thus the frontend drivers are listed seperately. 8 DVB-S/DVB-C/DVB-T. Thus the frontend drivers are listed separately.
9 9
10 Note 1: There is no guarantee that every frontend driver works 10 Note 1: There is no guarantee that every frontend driver works
11 out of the box with every card, because of different wiring. 11 out of the box with every card, because of different wiring.
diff --git a/Documentation/fb/sstfb.txt b/Documentation/fb/sstfb.txt
index ccdcfec3c346..df27f5bf15db 100644
--- a/Documentation/fb/sstfb.txt
+++ b/Documentation/fb/sstfb.txt
@@ -137,23 +137,23 @@ Bugs
137 - The driver is 16 bpp only, 24/32 won't work. 137 - The driver is 16 bpp only, 24/32 won't work.
138 - The driver is not your_favorite_toy-safe. this includes SMP... 138 - The driver is not your_favorite_toy-safe. this includes SMP...
139 [Actually from inspection it seems to be safe - Alan] 139 [Actually from inspection it seems to be safe - Alan]
140 - when using XFree86 FBdev (X over fbdev) you may see strange color 140 - When using XFree86 FBdev (X over fbdev) you may see strange color
141 patterns at the border of your windows (the pixels lose the lowest 141 patterns at the border of your windows (the pixels lose the lowest
142 byte -> basicaly the blue component nd some of the green) . I'm unable 142 byte -> basically the blue component and some of the green). I'm unable
143 to reproduce this with XFree86-3.3, but one of the testers has this 143 to reproduce this with XFree86-3.3, but one of the testers has this
144 problem with XFree86-4. apparently recent Xfree86-4.x solve this 144 problem with XFree86-4. Apparently recent Xfree86-4.x solve this
145 problem. 145 problem.
146 - I didn't really test changing the palette, so you may find some weird 146 - I didn't really test changing the palette, so you may find some weird
147 things when playing with that. 147 things when playing with that.
148 - Sometimes the driver will not recognise the DAC , and the 148 - Sometimes the driver will not recognise the DAC, and the
149 initialisation will fail. this is specificaly true for 149 initialisation will fail. This is specifically true for
150 voodoo 2 boards , but it should be solved in recent versions. please 150 voodoo 2 boards, but it should be solved in recent versions. Please
151 contact me . 151 contact me.
152 - the 24/32 is not likely to work anytime soon , knowing that the 152 - The 24/32 is not likely to work anytime soon, knowing that the
153 hardware does ... unusual thigs in 24/32 bpp 153 hardware does ... unusual things in 24/32 bpp.
154 - When used with anther video board, current limitations of linux 154 - When used with another video board, current limitations of the linux
155 console subsystem can cause some troubles, specificaly, you should 155 console subsystem can cause some troubles, specifically, you should
156 disable software scrollback , as it can oops badly ... 156 disable software scrollback, as it can oops badly ...
157 157
158Todo 158Todo
159 159
diff --git a/Documentation/filesystems/configfs/configfs.txt b/Documentation/filesystems/configfs/configfs.txt
index 8bf0369dcfb7..c3a7afb5eabf 100644
--- a/Documentation/filesystems/configfs/configfs.txt
+++ b/Documentation/filesystems/configfs/configfs.txt
@@ -254,7 +254,7 @@ using the group _init() functions on the group.
254 254
255Finally, when userspace calls rmdir(2) on the item or group, 255Finally, when userspace calls rmdir(2) on the item or group,
256ct_group_ops->drop_item() is called. As a config_group is also a 256ct_group_ops->drop_item() is called. As a config_group is also a
257config_item, it is not necessary for a seperate drop_group() method. 257config_item, it is not necessary for a separate drop_group() method.
258The subsystem must config_item_put() the reference that was initialized 258The subsystem must config_item_put() the reference that was initialized
259upon item allocation. If a subsystem has no work to do, it may omit 259upon item allocation. If a subsystem has no work to do, it may omit
260the ct_group_ops->drop_item() method, and configfs will call 260the ct_group_ops->drop_item() method, and configfs will call
diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
index 59763d695b14..3355e6920105 100644
--- a/Documentation/filesystems/proc.txt
+++ b/Documentation/filesystems/proc.txt
@@ -1255,7 +1255,7 @@ to allocate (but not use) more memory than is actually available.
1255 address space are refused. Used for a typical system. It 1255 address space are refused. Used for a typical system. It
1256 ensures a seriously wild allocation fails while allowing 1256 ensures a seriously wild allocation fails while allowing
1257 overcommit to reduce swap usage. root is allowed to 1257 overcommit to reduce swap usage. root is allowed to
1258 allocate slighly more memory in this mode. This is the 1258 allocate slightly more memory in this mode. This is the
1259 default. 1259 default.
1260 1260
12611 - Always overcommit. Appropriate for some scientific 12611 - Always overcommit. Appropriate for some scientific
@@ -1857,7 +1857,7 @@ proxy_qlen
1857 1857
1858Maximum queue length of the delayed proxy arp timer. (see proxy_delay). 1858Maximum queue length of the delayed proxy arp timer. (see proxy_delay).
1859 1859
1860app_solcit 1860app_solicit
1861---------- 1861----------
1862 1862
1863Determines the number of requests to send to the user level ARP daemon. Use 0 1863Determines the number of requests to send to the user level ARP daemon. Use 0
diff --git a/Documentation/hrtimers.txt b/Documentation/hrtimers.txt
index 1fbad1a7b809..ce31f65e12e7 100644
--- a/Documentation/hrtimers.txt
+++ b/Documentation/hrtimers.txt
@@ -58,7 +58,7 @@ several reasons why such integration is hard/impossible:
58The primary users of precision timers are user-space applications that 58The primary users of precision timers are user-space applications that
59utilize nanosleep, posix-timers and itimer interfaces. Also, in-kernel 59utilize nanosleep, posix-timers and itimer interfaces. Also, in-kernel
60users like drivers and subsystems which require precise timed events 60users like drivers and subsystems which require precise timed events
61(e.g. multimedia) can benefit from the availability of a seperate 61(e.g. multimedia) can benefit from the availability of a separate
62high-resolution timer subsystem as well. 62high-resolution timer subsystem as well.
63 63
64While this subsystem does not offer high-resolution clock sources just 64While this subsystem does not offer high-resolution clock sources just
@@ -68,7 +68,7 @@ The increasing demand for realtime and multimedia applications along
68with other potential users for precise timers gives another reason to 68with other potential users for precise timers gives another reason to
69separate the "timeout" and "precise timer" subsystems. 69separate the "timeout" and "precise timer" subsystems.
70 70
71Another potential benefit is that such a seperation allows even more 71Another potential benefit is that such a separation allows even more
72special-purpose optimization of the existing timer wheel for the low 72special-purpose optimization of the existing timer wheel for the low
73resolution and low precision use cases - once the precision-sensitive 73resolution and low precision use cases - once the precision-sensitive
74APIs are separated from the timer wheel and are migrated over to 74APIs are separated from the timer wheel and are migrated over to
@@ -96,8 +96,8 @@ file systems. The rbtree is solely used for time sorted ordering, while
96a separate list is used to give the expiry code fast access to the 96a separate list is used to give the expiry code fast access to the
97queued timers, without having to walk the rbtree. 97queued timers, without having to walk the rbtree.
98 98
99(This seperate list is also useful for later when we'll introduce 99(This separate list is also useful for later when we'll introduce
100high-resolution clocks, where we need seperate pending and expired 100high-resolution clocks, where we need separate pending and expired
101queues while keeping the time-order intact.) 101queues while keeping the time-order intact.)
102 102
103Time-ordered enqueueing is not purely for the purposes of 103Time-ordered enqueueing is not purely for the purposes of
diff --git a/Documentation/input/yealink.txt b/Documentation/input/yealink.txt
index 8bf2addadb4b..0a8c97e87d47 100644
--- a/Documentation/input/yealink.txt
+++ b/Documentation/input/yealink.txt
@@ -87,7 +87,7 @@ Line 3 Format : 888888888888
87 87
88 88
89Format description: 89Format description:
90 From a user space perspective the world is seperated in "digits" and "icons". 90 From a userspace perspective the world is separated into "digits" and "icons".
91 A digit can have a character set, an icon can only be ON or OFF. 91 A digit can have a character set, an icon can only be ON or OFF.
92 92
93 Format specifier 93 Format specifier
diff --git a/Documentation/kbuild/kconfig-language.txt b/Documentation/kbuild/kconfig-language.txt
index 003fccc14d24..7f34778dd23b 100644
--- a/Documentation/kbuild/kconfig-language.txt
+++ b/Documentation/kbuild/kconfig-language.txt
@@ -110,7 +110,7 @@ applicable everywhere (see syntax).
110 the indentation level, this means it ends at the first line which has 110 the indentation level, this means it ends at the first line which has
111 a smaller indentation than the first line of the help text. 111 a smaller indentation than the first line of the help text.
112 "---help---" and "help" do not differ in behaviour, "---help---" is 112 "---help---" and "help" do not differ in behaviour, "---help---" is
113 used to help visually seperate configuration logic from help within 113 used to help visually separate configuration logic from help within
114 the file as an aid to developers. 114 the file as an aid to developers.
115 115
116 116
@@ -226,7 +226,7 @@ menuconfig:
226 "menuconfig" <symbol> 226 "menuconfig" <symbol>
227 <config options> 227 <config options>
228 228
229This is similiar to the simple config entry above, but it also gives a 229This is similar to the simple config entry above, but it also gives a
230hint to front ends, that all suboptions should be displayed as a 230hint to front ends, that all suboptions should be displayed as a
231separate list of options. 231separate list of options.
232 232
diff --git a/Documentation/networking/slicecom.txt b/Documentation/networking/slicecom.txt
index 5fb21d5d46f0..2f04c9267f89 100644
--- a/Documentation/networking/slicecom.txt
+++ b/Documentation/networking/slicecom.txt
@@ -262,7 +262,7 @@ which begin with '//' are the comments.
262// initialised. 262// initialised.
263// AUXP - Auxiliary Pattern Indication - 01010101.. received. 263// AUXP - Auxiliary Pattern Indication - 01010101.. received.
264// LFA - Loss of Frame Alignment - no frame sync received. 264// LFA - Loss of Frame Alignment - no frame sync received.
265// RRA - Receive Remote Alarm - the remote end's OK, but singnals error cond. 265// RRA - Receive Remote Alarm - the remote end's OK, but signals error cond.
266// LMFA - Loss of CRC4 Multiframe Alignment - no CRC4 multiframe sync. 266// LMFA - Loss of CRC4 Multiframe Alignment - no CRC4 multiframe sync.
267// NMF - No Multiframe alignment Found after 400 msec - no such alarm using 267// NMF - No Multiframe alignment Found after 400 msec - no such alarm using
268// no-crc4 or crc4 framing, see below. 268// no-crc4 or crc4 framing, see below.
@@ -364,6 +364,6 @@ Treat them very carefully, these can cause much trouble!
364 364
365 # echo >lbireg 0x1d 0x21 365 # echo >lbireg 0x1d 0x21
366 366
367 - Swithing the loop off: 367 - Switching the loop off:
368 368
369 # echo >lbireg 0x1d 0x00 369 # echo >lbireg 0x1d 0x00
diff --git a/Documentation/networking/smctr.txt b/Documentation/networking/smctr.txt
index 4c866f5a0ee4..9af25b810c1f 100644
--- a/Documentation/networking/smctr.txt
+++ b/Documentation/networking/smctr.txt
@@ -11,7 +11,7 @@ This driver is rather simple to use. Select Y to Token Ring adapter support
11in the kernel configuration. A choice for SMC Token Ring adapters will 11in the kernel configuration. A choice for SMC Token Ring adapters will
12appear. This drives supports all SMC ISA/MCA adapters. Choose this 12appear. This drives supports all SMC ISA/MCA adapters. Choose this
13option. I personally recommend compiling the driver as a module (M), but if you 13option. I personally recommend compiling the driver as a module (M), but if you
14you would like to compile it staticly answer Y instead. 14you would like to compile it statically answer Y instead.
15 15
16This driver supports multiple adapters without the need to load multiple copies 16This driver supports multiple adapters without the need to load multiple copies
17of the driver. You should be able to load up to 7 adapters without any kernel 17of the driver. You should be able to load up to 7 adapters without any kernel
diff --git a/Documentation/networking/tms380tr.txt b/Documentation/networking/tms380tr.txt
index 179e527b9da1..c169a57bc925 100644
--- a/Documentation/networking/tms380tr.txt
+++ b/Documentation/networking/tms380tr.txt
@@ -24,7 +24,7 @@ This driver is rather simple to use. Select Y to Token Ring adapter support
24in the kernel configuration. A choice for SysKonnect Token Ring adapters will 24in the kernel configuration. A choice for SysKonnect Token Ring adapters will
25appear. This drives supports all SysKonnect ISA and PCI adapters. Choose this 25appear. This drives supports all SysKonnect ISA and PCI adapters. Choose this
26option. I personally recommend compiling the driver as a module (M), but if you 26option. I personally recommend compiling the driver as a module (M), but if you
27you would like to compile it staticly answer Y instead. 27you would like to compile it statically answer Y instead.
28 28
29This driver supports multiple adapters without the need to load multiple copies 29This driver supports multiple adapters without the need to load multiple copies
30of the driver. You should be able to load up to 7 adapters without any kernel 30of the driver. You should be able to load up to 7 adapters without any kernel
diff --git a/Documentation/power/tricks.txt b/Documentation/power/tricks.txt
index c6d58d3da133..3b26bb502a4a 100644
--- a/Documentation/power/tricks.txt
+++ b/Documentation/power/tricks.txt
@@ -9,7 +9,7 @@ If you want to trick swsusp/S3 into working, you might want to try:
9 9
10* turn off APIC and preempt 10* turn off APIC and preempt
11 11
12* use ext2. At least it has working fsck. [If something seemes to go 12* use ext2. At least it has working fsck. [If something seems to go
13 wrong, force fsck when you have a chance] 13 wrong, force fsck when you have a chance]
14 14
15* turn off modules 15* turn off modules
diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
index 8ca9a563e221..1ccc8a515b44 100644
--- a/Documentation/powerpc/booting-without-of.txt
+++ b/Documentation/powerpc/booting-without-of.txt
@@ -550,11 +550,11 @@ Here's the basic structure of a single node:
550 * [child nodes if any] 550 * [child nodes if any]
551 * token OF_DT_END_NODE (that is 0x00000002) 551 * token OF_DT_END_NODE (that is 0x00000002)
552 552
553So the node content can be summmarised as a start token, a full path, 553So the node content can be summarised as a start token, a full path,
554a list of properties, a list of child node and an end token. Every 554a list of properties, a list of child nodes, and an end token. Every
555child node is a full node structure itself as defined above. 555child node is a full node structure itself as defined above.
556 556
5574) Device tree 'strings" block 5574) Device tree "strings" block
558 558
559In order to save space, property names, which are generally redundant, 559In order to save space, property names, which are generally redundant,
560are stored separately in the "strings" block. This block is simply the 560are stored separately in the "strings" block. This block is simply the
diff --git a/Documentation/rocket.txt b/Documentation/rocket.txt
index 2d11ad6e525a..1d8582990435 100644
--- a/Documentation/rocket.txt
+++ b/Documentation/rocket.txt
@@ -97,7 +97,7 @@ a range of I/O addresses for it to use. The first RocketPort card
97requires a 68-byte contiguous block of I/O addresses, starting at one 97requires a 68-byte contiguous block of I/O addresses, starting at one
98of the following: 0x100h, 0x140h, 0x180h, 0x200h, 0x240h, 0x280h, 98of the following: 0x100h, 0x140h, 0x180h, 0x200h, 0x240h, 0x280h,
990x300h, 0x340h, 0x380h. This I/O address must be reflected in the DIP 990x300h, 0x340h, 0x380h. This I/O address must be reflected in the DIP
100switiches of *all* of the Rocketport cards. 100switches of *all* of the Rocketport cards.
101 101
102The second, third, and fourth RocketPort cards require a 64-byte 102The second, third, and fourth RocketPort cards require a 64-byte
103contiguous block of I/O addresses, starting at one of the following 103contiguous block of I/O addresses, starting at one of the following
diff --git a/Documentation/s390/Debugging390.txt b/Documentation/s390/Debugging390.txt
index 2d826d84943f..c051ba27670d 100644
--- a/Documentation/s390/Debugging390.txt
+++ b/Documentation/s390/Debugging390.txt
@@ -317,9 +317,9 @@ Each process/thread under Linux for S390 has its own kernel task_struct
317defined in linux/include/linux/sched.h 317defined in linux/include/linux/sched.h
318The S390 on initialisation & resuming of a process on a cpu sets 318The S390 on initialisation & resuming of a process on a cpu sets
319the __LC_KERNEL_STACK variable in the spare prefix area for this cpu 319the __LC_KERNEL_STACK variable in the spare prefix area for this cpu
320( which we use for per processor globals). 320(which we use for per-processor globals).
321 321
322The kernel stack pointer is intimately tied with the task stucture for 322The kernel stack pointer is intimately tied with the task structure for
323each processor as follows. 323each processor as follows.
324 324
325 s/390 325 s/390
@@ -973,8 +973,9 @@ through the pipe for each line containing the string open.
973 973
974Example 3 974Example 3
975--------- 975---------
976Getting sophistocated 976Getting sophisticated
977telnetd crashes on & I don't know why 977telnetd crashes & I don't know why
978
978Steps 979Steps
979----- 980-----
9801) Replace the following line in /etc/inetd.conf 9811) Replace the following line in /etc/inetd.conf
@@ -1836,7 +1837,7 @@ RDRLIST
1836RECEIVE / LOG TXT A1 ( replace 1837RECEIVE / LOG TXT A1 ( replace
18378) 18388)
1838filel & press F11 to look at it 1839filel & press F11 to look at it
1839You should see someting like. 1840You should see something like:
1840 1841
184100020942' SSCH B2334000 0048813C CC 0 SCH 0000 DEV 7C08 184200020942' SSCH B2334000 0048813C CC 0 SCH 0000 DEV 7C08
1842 CPA 000FFDF0 PARM 00E2C9C4 KEY 0 FPI C0 LPM 80 1843 CPA 000FFDF0 PARM 00E2C9C4 KEY 0 FPI C0 LPM 80
diff --git a/Documentation/s390/monreader.txt b/Documentation/s390/monreader.txt
index d843bb04906e..beeaa4b24427 100644
--- a/Documentation/s390/monreader.txt
+++ b/Documentation/s390/monreader.txt
@@ -83,7 +83,7 @@ This loads the module and sets the DCSS name to "MYDCSS".
83 83
84NOTE: 84NOTE:
85----- 85-----
86This API provides no interface to control the *MONITOR service, e.g. specifiy 86This API provides no interface to control the *MONITOR service, e.g. specify
87which data should be collected. This can be done by the CP command MONITOR 87which data should be collected. This can be done by the CP command MONITOR
88(Class E privileged), see "CP Command and Utility Reference". 88(Class E privileged), see "CP Command and Utility Reference".
89 89
diff --git a/Documentation/scsi/aacraid.txt b/Documentation/scsi/aacraid.txt
index ee03678c8029..3367130e64f6 100644
--- a/Documentation/scsi/aacraid.txt
+++ b/Documentation/scsi/aacraid.txt
@@ -4,7 +4,7 @@ Introduction
4------------------------- 4-------------------------
5The aacraid driver adds support for Adaptec (http://www.adaptec.com) 5The aacraid driver adds support for Adaptec (http://www.adaptec.com)
6RAID controllers. This is a major rewrite from the original 6RAID controllers. This is a major rewrite from the original
7Adaptec supplied driver. It has signficantly cleaned up both the code 7Adaptec supplied driver. It has significantly cleaned up both the code
8and the running binary size (the module is less than half the size of 8and the running binary size (the module is less than half the size of
9the original). 9the original).
10 10
diff --git a/Documentation/scsi/aic79xx.txt b/Documentation/scsi/aic79xx.txt
index 2084ad5efb94..904d49e90ef2 100644
--- a/Documentation/scsi/aic79xx.txt
+++ b/Documentation/scsi/aic79xx.txt
@@ -81,7 +81,7 @@ The following information is available in this file:
81 an SDTR with an offset of 0 to be sure the target 81 an SDTR with an offset of 0 to be sure the target
82 knows we are async. This works around a firmware defect 82 knows we are async. This works around a firmware defect
83 in the Quantum Atlas 10K. 83 in the Quantum Atlas 10K.
84 - Implement controller susupend and resume. 84 - Implement controller suspend and resume.
85 - Clear PCI error state during driver attach so that we 85 - Clear PCI error state during driver attach so that we
86 don't disable memory mapped I/O due to a stray write 86 don't disable memory mapped I/O due to a stray write
87 by some other driver probe that occurred before we 87 by some other driver probe that occurred before we
diff --git a/Documentation/scsi/aic7xxx_old.txt b/Documentation/scsi/aic7xxx_old.txt
index 1c8c69b8c465..c92f4473193b 100644
--- a/Documentation/scsi/aic7xxx_old.txt
+++ b/Documentation/scsi/aic7xxx_old.txt
@@ -241,7 +241,7 @@ linux-1.1.x and fairly stable since linux-1.2.x, and are also in FreeBSD
241 that instead of dumping the register contents on the card, this 241 that instead of dumping the register contents on the card, this
242 option dumps the contents of the sequencer program RAM. This gives 242 option dumps the contents of the sequencer program RAM. This gives
243 the ability to verify that the instructions downloaded to the 243 the ability to verify that the instructions downloaded to the
244 card's sequencer are indeed what they are suppossed to be. Again, 244 card's sequencer are indeed what they are supposed to be. Again,
245 unless you have documentation to tell you how to interpret these 245 unless you have documentation to tell you how to interpret these
246 numbers, then it is totally useless. 246 numbers, then it is totally useless.
247 247
diff --git a/Documentation/scsi/ibmmca.txt b/Documentation/scsi/ibmmca.txt
index 9b9516364ec1..35f6b8ed2295 100644
--- a/Documentation/scsi/ibmmca.txt
+++ b/Documentation/scsi/ibmmca.txt
@@ -309,9 +309,9 @@
309 2.6 Abort & Reset Commands 309 2.6 Abort & Reset Commands
310 -------------------------- 310 --------------------------
311 These are implemented with busy waiting for interrupt to arrive. 311 These are implemented with busy waiting for interrupt to arrive.
312 ibmmca_reset() and ibmmca_abort() do not work sufficently well 312 ibmmca_reset() and ibmmca_abort() do not work sufficiently well
313 up to now and need still a lot of development work. But, this seems 313 up to now and need still a lot of development work. This seems
314 to be even a problem with other SCSI-low level drivers, too. However, 314 to be a problem with other low-level SCSI drivers too, however
315 this should be no excuse. 315 this should be no excuse.
316 316
317 2.7 Disk Geometry 317 2.7 Disk Geometry
@@ -684,8 +684,8 @@
684 not like sending commands to non-existing SCSI-devices and will react 684 not like sending commands to non-existing SCSI-devices and will react
685 with a command error as a sign of protest. While this error is not 685 with a command error as a sign of protest. While this error is not
686 present on IBM SCSI Adapter w/cache, it appears on IBM Integrated SCSI 686 present on IBM SCSI Adapter w/cache, it appears on IBM Integrated SCSI
687 Adapters. Therefore, I implemented a workarround to forgive those 687 Adapters. Therefore, I implemented a workaround to forgive those
688 adapters their protests, but it is marked up in the statisctis, so 688 adapters their protests, but it is marked up in the statistics, so
689 after a successful boot, you can see in /proc/scsi/ibmmca/<host_number> 689 after a successful boot, you can see in /proc/scsi/ibmmca/<host_number>
690 how often the command errors have been forgiven to the SCSI-subsystem. 690 how often the command errors have been forgiven to the SCSI-subsystem.
691 If the number is bigger than 0, you have a SCSI subsystem of older 691 If the number is bigger than 0, you have a SCSI subsystem of older
@@ -778,15 +778,15 @@
778 not accept this, as they stick quite near to ANSI-SCSI and report 778 not accept this, as they stick quite near to ANSI-SCSI and report
779 a COMMAND_ERROR message which causes the driver to panic. The main 779 a COMMAND_ERROR message which causes the driver to panic. The main
780 problem was located around the INQUIRY command. Now, for all the 780 problem was located around the INQUIRY command. Now, for all the
781 mentioned commands, the buffersize, sent to the adapter is at 781 mentioned commands, the buffersize sent to the adapter is at
782 maximum 255 which seems to be a quite reasonable solution. 782 maximum 255 which seems to be a quite reasonable solution.
783 TEST_UNIT_READY gets a buffersize of 0 to make sure, that no 783 TEST_UNIT_READY gets a buffersize of 0 to make sure that no
784 data is transferred in order to avoid any possible command failure. 784 data is transferred in order to avoid any possible command failure.
785 2) On unsuccessful TEST_UNIT_READY, the midlevel-driver has to send 785 2) On unsuccessful TEST_UNIT_READY, the mid-level driver has to send
786 a REQUEST_SENSE in order to see, where the problem is located. This 786 a REQUEST_SENSE in order to see where the problem is located. This
787 REQUEST_SENSE may have various length in its answer-buffer. IBM 787 REQUEST_SENSE may have various length in its answer-buffer. IBM
788 SCSI-subsystems report a command failure, if the returned buffersize 788 SCSI-subsystems report a command failure if the returned buffersize
789 is different from the sent buffersize, but this can be supressed by 789 is different from the sent buffersize, but this can be suppressed by
790 a special bit, which is now done and problems seem to be solved. 790 a special bit, which is now done and problems seem to be solved.
791 2) Code adaption to all kernel-releases. Now, the 3.2 code compiles on 791 2) Code adaption to all kernel-releases. Now, the 3.2 code compiles on
792 2.0.x, 2.1.x, 2.2.x and 2.3.x kernel releases without any code-changes. 792 2.0.x, 2.1.x, 2.2.x and 2.3.x kernel releases without any code-changes.
@@ -1156,7 +1156,7 @@
1156 Guide) what has to be done for reset, we still share the bad shape of 1156 Guide) what has to be done for reset, we still share the bad shape of
1157 the reset functions with all other low level SCSI-drivers. 1157 the reset functions with all other low level SCSI-drivers.
1158 Astonishingly, reset works in most cases quite ok, but the harddisks 1158 Astonishingly, reset works in most cases quite ok, but the harddisks
1159 won't run in synchonous mode anymore after a reset, until you reboot. 1159 won't run in synchronous mode anymore after a reset, until you reboot.
1160 Q: Why does my XXX w/Cache adapter not use read-prefetch? 1160 Q: Why does my XXX w/Cache adapter not use read-prefetch?
1161 A: Ok, that is not completely possible. If a cache is present, the 1161 A: Ok, that is not completely possible. If a cache is present, the
1162 adapter tries to use it internally. Explicitly, one can use the cache 1162 adapter tries to use it internally. Explicitly, one can use the cache
diff --git a/Documentation/scsi/ncr53c8xx.txt b/Documentation/scsi/ncr53c8xx.txt
index ea8e98fad2bb..58ad8db333d9 100644
--- a/Documentation/scsi/ncr53c8xx.txt
+++ b/Documentation/scsi/ncr53c8xx.txt
@@ -70,7 +70,7 @@ Written by Gerard Roudier <groudier@free.fr>
7015. SCSI problem troubleshooting 7015. SCSI problem troubleshooting
71 15.1 Problem tracking 71 15.1 Problem tracking
72 15.2 Understanding hardware error reports 72 15.2 Understanding hardware error reports
7316. Synchonous transfer negotiation tables 7316. Synchronous transfer negotiation tables
74 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers 74 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
75 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers 75 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers
7617. Serial NVRAM support (by Richard Waltham) 7617. Serial NVRAM support (by Richard Waltham)
@@ -1382,7 +1382,7 @@ SCSI standards, chip cores functionnals and internal driver data structures.
1382You are not required to decode and understand them, unless you want to help 1382You are not required to decode and understand them, unless you want to help
1383maintain the driver code. 1383maintain the driver code.
1384 1384
138516. Synchonous transfer negotiation tables 138516. Synchronous transfer negotiation tables
1386 1386
1387Tables below have been created by calling the routine the driver uses 1387Tables below have been created by calling the routine the driver uses
1388for synchronisation negotiation timing calculation and chip setting. 1388for synchronisation negotiation timing calculation and chip setting.
diff --git a/Documentation/scsi/st.txt b/Documentation/scsi/st.txt
index 20e30cf31877..66ba3ad0ce06 100644
--- a/Documentation/scsi/st.txt
+++ b/Documentation/scsi/st.txt
@@ -369,7 +369,7 @@ MTSETDRVBUFFER
369 the device dependent address. It is recommended to set 369 the device dependent address. It is recommended to set
370 this flag unless there are tapes using the device 370 this flag unless there are tapes using the device
371 dependent (from the old times) (global) 371 dependent (from the old times) (global)
372 MT_ST_SYSV sets the SYSV sematics (mode) 372 MT_ST_SYSV sets the SYSV semantics (mode)
373 MT_ST_NOWAIT enables immediate mode (i.e., don't wait for 373 MT_ST_NOWAIT enables immediate mode (i.e., don't wait for
374 the command to finish) for some commands (e.g., rewind) 374 the command to finish) for some commands (e.g., rewind)
375 MT_ST_DEBUGGING debugging (global; debugging must be 375 MT_ST_DEBUGGING debugging (global; debugging must be
diff --git a/Documentation/scsi/sym53c8xx_2.txt b/Documentation/scsi/sym53c8xx_2.txt
index 98d5f1ec124f..26c8a08ca3ea 100644
--- a/Documentation/scsi/sym53c8xx_2.txt
+++ b/Documentation/scsi/sym53c8xx_2.txt
@@ -67,7 +67,7 @@ under Linux is contained in 2 files named sym_glue.h and sym_glue.c.
67Other drivers files are intended not to depend on the Operating System 67Other drivers files are intended not to depend on the Operating System
68on which the driver is used. 68on which the driver is used.
69 69
70The history of this driver can be summerized as follows: 70The history of this driver can be summarized as follows:
71 71
721993: ncr driver written for 386bsd and FreeBSD by: 721993: ncr driver written for 386bsd and FreeBSD by:
73 Wolfgang Stanglmeier <wolf@cologne.de> 73 Wolfgang Stanglmeier <wolf@cologne.de>
diff --git a/Documentation/sound/alsa/CMIPCI.txt b/Documentation/sound/alsa/CMIPCI.txt
index 4cae0474b104..4b2b15387056 100644
--- a/Documentation/sound/alsa/CMIPCI.txt
+++ b/Documentation/sound/alsa/CMIPCI.txt
@@ -16,11 +16,11 @@ As default, ALSA driver assigns the first PCM device (i.e. hw:0,0 for
16card#0) for front and 4/6ch playbacks, while the second PCM device 16card#0) for front and 4/6ch playbacks, while the second PCM device
17(hw:0,1) is assigned to the second DAC for rear playback. 17(hw:0,1) is assigned to the second DAC for rear playback.
18 18
19There are slight difference between two DACs. 19There are slight differences between the two DACs:
20 20
21- The first DAC supports U8 and S16LE formats, while the second DAC 21- The first DAC supports U8 and S16LE formats, while the second DAC
22 supports only S16LE. 22 supports only S16LE.
23- The seconde DAC supports only two channel stereo. 23- The second DAC supports only two channel stereo.
24 24
25Please note that the CM8x38 DAC doesn't support continuous playback 25Please note that the CM8x38 DAC doesn't support continuous playback
26rate but only fixed rates: 5512, 8000, 11025, 16000, 22050, 32000, 26rate but only fixed rates: 5512, 8000, 11025, 16000, 22050, 32000,
diff --git a/Documentation/sound/alsa/MIXART.txt b/Documentation/sound/alsa/MIXART.txt
index 9fa5bbdbac82..ef42c44fa1f2 100644
--- a/Documentation/sound/alsa/MIXART.txt
+++ b/Documentation/sound/alsa/MIXART.txt
@@ -39,7 +39,7 @@ For instance the playback devices are configured to have max. 4
39substreams performing hardware mixing. This could be changed to a 39substreams performing hardware mixing. This could be changed to a
40maximum of 24 substreams if wished. 40maximum of 24 substreams if wished.
41Mono files will be played on the left and right channel. Each channel 41Mono files will be played on the left and right channel. Each channel
42can be muted for each stream to use 8 analog/digital outputs seperately. 42can be muted for each stream to use 8 analog/digital outputs separately.
43 43
44Capture 44Capture
45------- 45-------
diff --git a/Documentation/sound/alsa/Procfile.txt b/Documentation/sound/alsa/Procfile.txt
index 18f04bd1b9a0..f738b296440a 100644
--- a/Documentation/sound/alsa/Procfile.txt
+++ b/Documentation/sound/alsa/Procfile.txt
@@ -161,12 +161,12 @@ seq/drivers
161 Lists the currently available ALSA sequencer drivers. 161 Lists the currently available ALSA sequencer drivers.
162 162
163seq/clients 163seq/clients
164 Shows the list of currently available sequencer clinets and 164 Shows the list of currently available sequencer clients and
165 ports. The connection status and the running status are shown 165 ports. The connection status and the running status are shown
166 in this file, too. 166 in this file, too.
167 167
168seq/queues 168seq/queues
169 Lists the currently allocated/running sequener queues. 169 Lists the currently allocated/running sequencer queues.
170 170
171seq/timer 171seq/timer
172 Lists the currently allocated/running sequencer timers. 172 Lists the currently allocated/running sequencer timers.
diff --git a/Documentation/usb/URB.txt b/Documentation/usb/URB.txt
index a49e5f2c2b46..8ffce746d496 100644
--- a/Documentation/usb/URB.txt
+++ b/Documentation/usb/URB.txt
@@ -184,7 +184,7 @@ you can pass information to the completion handler.
184Note that even when an error (or unlink) is reported, data may have been 184Note that even when an error (or unlink) is reported, data may have been
185transferred. That's because USB transfers are packetized; it might take 185transferred. That's because USB transfers are packetized; it might take
186sixteen packets to transfer your 1KByte buffer, and ten of them might 186sixteen packets to transfer your 1KByte buffer, and ten of them might
187have transferred succesfully before the completion was called. 187have transferred successfully before the completion was called.
188 188
189 189
190NOTE: ***** WARNING ***** 190NOTE: ***** WARNING *****
diff --git a/Documentation/usb/mtouchusb.txt b/Documentation/usb/mtouchusb.txt
index 9edf23560516..e43cfffaa100 100644
--- a/Documentation/usb/mtouchusb.txt
+++ b/Documentation/usb/mtouchusb.txt
@@ -11,7 +11,7 @@ CHANGES
11 Changed reset from standard USB dev reset to vendor reset 11 Changed reset from standard USB dev reset to vendor reset
12 Changed data sent to host from compensated to raw coordinates 12 Changed data sent to host from compensated to raw coordinates
13 Eliminated vendor/product module params 13 Eliminated vendor/product module params
14 Performed multiple successfull tests with an EXII-5010UC 14 Performed multiple successful tests with an EXII-5010UC
15 15
16SUPPORTED HARDWARE: 16SUPPORTED HARDWARE:
17 17