lk/linux-kernel-test
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix typos in /Documentation : 'U-Z'

Browse Source 
This patch fixes typos in various Documentation txts. The patch addresses some
+words starting with the letters 'U-Z'.

Looks like I made it through the alphabet...just in time to start over again
+too!  Maybe I can fit more profound fixes into the next round...?  Time will
+tell. :)

Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
This commit is contained in:
Matt LaPlante
2006-11-30 04:58:40 +01:00
committed by Adrian Bunk
parent fa00e7e152
commit 4ae0edc21b
27 changed files with 38 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/DMA-API.txt
View File

@@ -489,7 +489,7 @@ size is the size of the area (must be multiples of PAGE_SIZE).
flags can be or'd together and are flags can be or'd together and are
DMA_MEMORY_MAP - request that the memory returned from DMA_MEMORY_MAP - request that the memory returned from
dma_alloc_coherent() be directly writeable. dma_alloc_coherent() be directly writable.
DMA_MEMORY_IO - request that the memory returned from DMA_MEMORY_IO - request that the memory returned from
dma_alloc_coherent() be addressable using read/write/memcpy_toio etc. dma_alloc_coherent() be addressable using read/write/memcpy_toio etc.

2
Documentation/MSI-HOWTO.txt
View File

@@ -219,7 +219,7 @@ into the field vector of each element contained in a second argument.
Note that the pre-assigned IOAPIC dev->irq is valid only if the device Note that the pre-assigned IOAPIC dev->irq is valid only if the device
operates in PIN-IRQ assertion mode. In MSI-X mode, any attempt at operates in PIN-IRQ assertion mode. In MSI-X mode, any attempt at
using dev->irq by the device driver to request for interrupt service using dev->irq by the device driver to request for interrupt service
may result unpredictabe behavior. may result in unpredictable behavior.
For each MSI-X vector granted, a device driver is responsible for calling For each MSI-X vector granted, a device driver is responsible for calling
other functions like request_irq(), enable_irq(), etc. to enable other functions like request_irq(), enable_irq(), etc. to enable

6
Documentation/accounting/taskstats.txt
View File

@@ -122,12 +122,12 @@ of atomicity).
However, maintaining per-process, in addition to per-task stats, within the However, maintaining per-process, in addition to per-task stats, within the
kernel has space and time overheads. To address this, the taskstats code kernel has space and time overheads. To address this, the taskstats code
accumalates each exiting task's statistics into a process-wide data structure. accumulates each exiting task's statistics into a process-wide data structure.
When the last task of a process exits, the process level data accumalated also When the last task of a process exits, the process level data accumulated also
gets sent to userspace (along with the per-task data). gets sent to userspace (along with the per-task data).
When a user queries to get per-tgid data, the sum of all other live threads in When a user queries to get per-tgid data, the sum of all other live threads in
the group is added up and added to the accumalated total for previously exited the group is added up and added to the accumulated total for previously exited
threads of the same thread group. threads of the same thread group.
Extending taskstats Extending taskstats

6
Documentation/block/biodoc.txt
View File

@@ -391,7 +391,7 @@ forced such requests to be broken up into small chunks before being passed
on to the generic block layer, only to be merged by the i/o scheduler on to the generic block layer, only to be merged by the i/o scheduler
when the underlying device was capable of handling the i/o in one shot. when the underlying device was capable of handling the i/o in one shot.
Also, using the buffer head as an i/o structure for i/os that didn't originate Also, using the buffer head as an i/o structure for i/os that didn't originate
from the buffer cache unecessarily added to the weight of the descriptors from the buffer cache unnecessarily added to the weight of the descriptors
which were generated for each such chunk. which were generated for each such chunk.
The following were some of the goals and expectations considered in the The following were some of the goals and expectations considered in the
@@ -403,14 +403,14 @@ i. Should be appropriate as a descriptor for both raw and buffered i/o -
for raw i/o. for raw i/o.
ii. Ability to represent high-memory buffers (which do not have a virtual ii. Ability to represent high-memory buffers (which do not have a virtual
address mapping in kernel address space). address mapping in kernel address space).
iii.Ability to represent large i/os w/o unecessarily breaking them up (i.e iii.Ability to represent large i/os w/o unnecessarily breaking them up (i.e
greater than PAGE_SIZE chunks in one shot) greater than PAGE_SIZE chunks in one shot)
iv. At the same time, ability to retain independent identity of i/os from iv. At the same time, ability to retain independent identity of i/os from
different sources or i/o units requiring individual completion (e.g. for different sources or i/o units requiring individual completion (e.g. for
latency reasons) latency reasons)
v. Ability to represent an i/o involving multiple physical memory segments v. Ability to represent an i/o involving multiple physical memory segments
(including non-page aligned page fragments, as specified via readv/writev) (including non-page aligned page fragments, as specified via readv/writev)
without unecessarily breaking it up, if the underlying device is capable of without unnecessarily breaking it up, if the underlying device is capable of
handling it. handling it.
vi. Preferably should be based on a memory descriptor structure that can be vi. Preferably should be based on a memory descriptor structure that can be
passed around different types of subsystems or layers, maybe even passed around different types of subsystems or layers, maybe even

4
Documentation/dvb/ci.txt
View File

@@ -71,7 +71,7 @@ eliminating the need for any additional ioctls.
The disadvantage is that the driver/hardware has to manage the rest. For The disadvantage is that the driver/hardware has to manage the rest. For
the application programmer it would be as simple as sending/receiving an the application programmer it would be as simple as sending/receiving an
array to/from the CI ioctls as defined in the Linux DVB API. No changes array to/from the CI ioctls as defined in the Linux DVB API. No changes
have been made in the API to accomodate this feature. have been made in the API to accommodate this feature.
* Why the need for another CI interface ? * Why the need for another CI interface ?
@@ -102,7 +102,7 @@ This CI interface follows the CI high level interface, which is not
implemented by most applications. Hence this area is revisited. implemented by most applications. Hence this area is revisited.
This CI interface is quite different in the case that it tries to This CI interface is quite different in the case that it tries to
accomodate all other CI based devices, that fall into the other categories accommodate all other CI based devices, that fall into the other categories.
This means that this CI interface handles the EN50221 style tags in the This means that this CI interface handles the EN50221 style tags in the
Application layer only and no session management is taken care of by the Application layer only and no session management is taken care of by the

2
Documentation/eisa.txt
View File

@@ -62,7 +62,7 @@ res : root device I/O resource
bus_base_addr : slot 0 address on this bus bus_base_addr : slot 0 address on this bus
slots : max slot number to probe slots : max slot number to probe
force_probe : Probe even when slot 0 is empty (no EISA mainboard) force_probe : Probe even when slot 0 is empty (no EISA mainboard)
dma_mask : Default DMA mask. Usualy the bridge device dma_mask. dma_mask : Default DMA mask. Usually the bridge device dma_mask.
bus_nr : unique bus id, set by eisa_root_register bus_nr : unique bus id, set by eisa_root_register
** Driver : ** Driver :

2
Documentation/filesystems/adfs.txt
View File

@@ -3,7 +3,7 @@ Mount options for ADFS
uid=nnn All files in the partition will be owned by uid=nnn All files in the partition will be owned by
user id nnn. Default 0 (root). user id nnn. Default 0 (root).
gid=nnn All files in the partition willbe in group gid=nnn All files in the partition will be in group
nnn. Default 0 (root). nnn. Default 0 (root).
ownmask=nnn The permission mask for ADFS 'owner' permissions ownmask=nnn The permission mask for ADFS 'owner' permissions
will be nnn. Default 0700. will be nnn. Default 0700.

4
Documentation/filesystems/configfs/configfs.txt
View File

@@ -209,7 +209,7 @@ will happen for write(2).
[struct config_group] [struct config_group]
A config_item cannot live in a vaccum. The only way one can be created A config_item cannot live in a vacuum. The only way one can be created
is via mkdir(2) on a config_group. This will trigger creation of a is via mkdir(2) on a config_group. This will trigger creation of a
child item. child item.
@@ -275,7 +275,7 @@ directory is not empty.
[struct configfs_subsystem] [struct configfs_subsystem]
A subsystem must register itself, ususally at module_init time. This A subsystem must register itself, usually at module_init time. This
tells configfs to make the subsystem appear in the file tree. tells configfs to make the subsystem appear in the file tree.
struct configfs_subsystem { struct configfs_subsystem {

2
Documentation/filesystems/hpfs.txt
View File

@@ -274,7 +274,7 @@ History
Fixed race-condition in buffer code - it is in all filesystems in Linux; Fixed race-condition in buffer code - it is in all filesystems in Linux;
when reading device (cat /dev/hda) while creating files on it, files when reading device (cat /dev/hda) while creating files on it, files
could be damaged could be damaged
2.02 Woraround for bug in breada in Linux. breada could cause accesses beyond 2.02 Workaround for bug in breada in Linux. breada could cause accesses beyond
end of partition end of partition
2.03 Char, block devices and pipes are correctly created 2.03 Char, block devices and pipes are correctly created
Fixed non-crashing race in unlink (Alexander Viro) Fixed non-crashing race in unlink (Alexander Viro)

2
Documentation/filesystems/ocfs2.txt
View File

@@ -30,7 +30,7 @@ Caveats
Features which OCFS2 does not support yet: Features which OCFS2 does not support yet:
- sparse files - sparse files
- extended attributes - extended attributes
- shared writeable mmap - shared writable mmap
- loopback is supported, but data written will not - loopback is supported, but data written will not
be cluster coherent. be cluster coherent.
- quotas - quotas

4
Documentation/filesystems/proc.txt
View File

@@ -1220,9 +1220,9 @@ applications are using mlock(), or if you are running with no swap then
you probably should increase the lower_zone_protection setting. you probably should increase the lower_zone_protection setting.
The units of this tunable are fairly vague. It is approximately equal The units of this tunable are fairly vague. It is approximately equal
to "megabytes". So setting lower_zone_protection=100 will protect around 100 to "megabytes," so setting lower_zone_protection=100 will protect around 100
megabytes of the lowmem zone from user allocations. It will also make megabytes of the lowmem zone from user allocations. It will also make
those 100 megabytes unavaliable for use by applications and by those 100 megabytes unavailable for use by applications and by
pagecache, so there is a cost. pagecache, so there is a cost.
The effects of this tunable may be observed by monitoring The effects of this tunable may be observed by monitoring

2
Documentation/filesystems/spufs.txt
View File

@@ -210,7 +210,7 @@ FILES
/signal2 /signal2
The two signal notification channels of an SPU. These are read-write The two signal notification channels of an SPU. These are read-write
files that operate on a 32 bit word. Writing to one of these files files that operate on a 32 bit word. Writing to one of these files
triggers an interrupt on the SPU. The value writting to the signal triggers an interrupt on the SPU. The value written to the signal
files can be read from the SPU through a channel read or from host user files can be read from the SPU through a channel read or from host user
space through the file. After the value has been read by the SPU, it space through the file. After the value has been read by the SPU, it
is reset to zero. The possible operations on an open signal1 or sig- is reset to zero. The possible operations on an open signal1 or sig-

2
Documentation/ide.txt
View File

@@ -390,5 +390,5 @@ mlord@pobox.com
Wed Apr 17 22:52:44 CEST 2002 edited by Marcin Dalecki, the current Wed Apr 17 22:52:44 CEST 2002 edited by Marcin Dalecki, the current
maintainer. maintainer.
Wed Aug 20 22:31:29 CEST 2003 updated ide boot uptions to current ide.c Wed Aug 20 22:31:29 CEST 2003 updated ide boot options to current ide.c
comments at 2.6.0-test4 time. Maciej Soltysiak <solt@dns.toxicfilms.tv> comments at 2.6.0-test4 time. Maciej Soltysiak <solt@dns.toxicfilms.tv>

2
Documentation/input/atarikbd.txt
View File

@@ -103,7 +103,7 @@ LEFT=0x74 & RIGHT=0x75).
5.1 Joystick Event Reporting 5.1 Joystick Event Reporting
In this mode, the ikbd generates a record whever the joystick position is In this mode, the ikbd generates a record whenever the joystick position is
changed (i.e. for each opening or closing of a joystick switch or trigger). changed (i.e. for each opening or closing of a joystick switch or trigger).
The joystick event record is two bytes of the form: The joystick event record is two bytes of the form:

2
Documentation/ioctl/cdrom.txt
View File

@@ -735,7 +735,7 @@ CDROM_DISC_STATUS Get disc type, etc.
Ok, this is where problems start. The current interface for Ok, this is where problems start. The current interface for
the CDROM_DISC_STATUS ioctl is flawed. It makes the false the CDROM_DISC_STATUS ioctl is flawed. It makes the false
assumption that CDs are all CDS_DATA_1 or all CDS_AUDIO, etc. assumption that CDs are all CDS_DATA_1 or all CDS_AUDIO, etc.
Unfortunatly, while this is often the case, it is also Unfortunately, while this is often the case, it is also
very common for CDs to have some tracks with data, and some very common for CDs to have some tracks with data, and some
tracks with audio. Just because I feel like it, I declare tracks with audio. Just because I feel like it, I declare
the following to be the best way to cope. If the CD has the following to be the best way to cope. If the CD has

2
Documentation/laptop-mode.txt
View File

@@ -699,7 +699,7 @@ ACPI integration
Dax Kelson submitted this so that the ACPI acpid daemon will Dax Kelson submitted this so that the ACPI acpid daemon will
kick off the laptop_mode script and run hdparm. The part that kick off the laptop_mode script and run hdparm. The part that
automatically disables laptop mode when the battery is low was automatically disables laptop mode when the battery is low was
writen by Jan Topinski. written by Jan Topinski.
-----------------/etc/acpi/events/ac_adapter BEGIN------------------------------ -----------------/etc/acpi/events/ac_adapter BEGIN------------------------------
event=ac_adapter event=ac_adapter

8
Documentation/networking/NAPI_HOWTO.txt
View File

@@ -601,7 +601,7 @@ a)
5) dev->close() and dev->suspend() issues 5) dev->close() and dev->suspend() issues
========================================== ==========================================
The driver writter neednt worry about this. The top net layer takes The driver writer needn't worry about this; the top net layer takes
care of it. care of it.
6) Adding new Stats to /proc 6) Adding new Stats to /proc
@@ -622,9 +622,9 @@ FC should be programmed to apply in the case when the system cant pull out
packets fast enough i.e send a pause only when you run out of rx buffers. packets fast enough i.e send a pause only when you run out of rx buffers.
Note FC in itself is a good solution but we have found it to not be Note FC in itself is a good solution but we have found it to not be
much of a commodity feature (both in NICs and switches) and hence falls much of a commodity feature (both in NICs and switches) and hence falls
under the same category as using NIC based mitigation. Also experiments under the same category as using NIC based mitigation. Also, experiments
indicate that its much harder to resolve the resource allocation indicate that it's much harder to resolve the resource allocation
issue (aka lazy receiving that NAPI offers) and hence quantify its usefullness issue (aka lazy receiving that NAPI offers) and hence quantify its usefulness
proved harder. In any case, FC works even better with NAPI but is not proved harder. In any case, FC works even better with NAPI but is not
necessary. necessary.

2
Documentation/networking/sk98lin.txt
View File

@@ -346,7 +346,7 @@ Possible modes:
depending on the load of the system. If the driver detects that the depending on the load of the system. If the driver detects that the
system load is too high, the driver tries to shield the system against system load is too high, the driver tries to shield the system against
too much network load by enabling interrupt moderation. If - at a later too much network load by enabling interrupt moderation. If - at a later
time - the CPU utilizaton decreases again (or if the network load is time - the CPU utilization decreases again (or if the network load is
negligible) the interrupt moderation will automatically be disabled. negligible) the interrupt moderation will automatically be disabled.
Interrupt moderation should be used when the driver has to handle one or more Interrupt moderation should be used when the driver has to handle one or more

2
Documentation/networking/slicecom.txt
View File

@@ -126,7 +126,7 @@ comx0/boardnum - board number of the SliceCom in the PC (using the 'natural'
Though the options below are to be set on a single interface, they apply to the Though the options below are to be set on a single interface, they apply to the
whole board. The restriction, to use them on 'UP' interfaces, is because the whole board. The restriction, to use them on 'UP' interfaces, is because the
command sequence below could lead to unpredicable results. command sequence below could lead to unpredictable results.
# echo 0 >boardnum # echo 0 >boardnum
# echo internal >clock_source # echo internal >clock_source

4
Documentation/networking/wan-router.txt
View File

@@ -412,7 +412,7 @@ beta-2.1.4 Jul 2000 o Dynamic interface configuration:
beta3-2.1.4 Jul 2000 o X25 M_BIT Problem fix. beta3-2.1.4 Jul 2000 o X25 M_BIT Problem fix.
o Added the Multi-Port PPP o Added the Multi-Port PPP
Updated utilites for the Multi-Port PPP. Updated utilities for the Multi-Port PPP.
2.1.4 Aut 2000 2.1.4 Aut 2000
o In X25API: o In X25API:
@@ -450,7 +450,7 @@ beta1-2.1.5 Nov 15 2000
o Keyboard Led Monitor/Debugger o Keyboard Led Monitor/Debugger
- A new utilty /usr/sbin/wpkbdmon uses keyboard leds - A new utility /usr/sbin/wpkbdmon uses keyboard leds
to convey operational statistic information of the to convey operational statistic information of the
Sangoma WANPIPE cards. Sangoma WANPIPE cards.
NUM_LOCK = Line State (On=connected, Off=disconnected) NUM_LOCK = Line State (On=connected, Off=disconnected)

2
Documentation/pnp.txt
View File

@@ -184,7 +184,7 @@ static const struct pnp_id pnp_dev_table[] = {
Please note that the character 'X' can be used as a wild card in the function Please note that the character 'X' can be used as a wild card in the function
portion (last four characters). portion (last four characters).
ex: ex:
/* Unkown PnP modems */ /* Unknown PnP modems */
{ "PNPCXXX", UNKNOWN_DEV }, { "PNPCXXX", UNKNOWN_DEV },
Supported PnP card IDs can optionally be defined. Supported PnP card IDs can optionally be defined.

2
Documentation/robust-futex-ABI.txt
View File

@@ -170,7 +170,7 @@ any point:
1) the 'head' pointer or an subsequent linked list pointer 1) the 'head' pointer or an subsequent linked list pointer
is not a valid address of a user space word is not a valid address of a user space word
2) the calculated location of the 'lock word' (address plus 2) the calculated location of the 'lock word' (address plus
'offset') is not the valud address of a 32 bit user space 'offset') is not the valid address of a 32 bit user space
word word
3) if the list contains more than 1 million (subject to 3) if the list contains more than 1 million (subject to
future kernel configuration changes) elements. future kernel configuration changes) elements.

2
Documentation/scsi/ibmmca.txt
View File

@@ -461,7 +461,7 @@
This needs the RD-Bit to be disabled on IM_OTHER_SCSI_CMD_CMD which This needs the RD-Bit to be disabled on IM_OTHER_SCSI_CMD_CMD which
allows data to be written from the system to the device. It is a allows data to be written from the system to the device. It is a
necessary step to be allowed to set blocksize of SCSI-tape-drives and necessary step to be allowed to set blocksize of SCSI-tape-drives and
the tape-speed, whithout confusing the SCSI-Subsystem. the tape-speed, without confusing the SCSI-Subsystem.
2) The recognition of a tape is included in the check_devices routine. 2) The recognition of a tape is included in the check_devices routine.
This is done by checking for TYPE_TAPE, that is already defined in This is done by checking for TYPE_TAPE, that is already defined in
the kernel-scsi-environment. The markup of a tape is done in the the kernel-scsi-environment. The markup of a tape is done in the

2
Documentation/scsi/ncr53c8xx.txt
View File

@@ -115,7 +115,7 @@ SCSI standard documentations are available at SYMBIOS ftp server:
ftp://ftp.symbios.com/ ftp://ftp.symbios.com/
Usefull SCSI tools written by Eric Youngdale are available at tsx-11: Useful SCSI tools written by Eric Youngdale are available at tsx-11:
ftp://tsx-11.mit.edu/pub/linux/ALPHA/scsi/scsiinfo-X.Y.tar.gz ftp://tsx-11.mit.edu/pub/linux/ALPHA/scsi/scsiinfo-X.Y.tar.gz
ftp://tsx-11.mit.edu/pub/linux/ALPHA/scsi/scsidev-X.Y.tar.gz ftp://tsx-11.mit.edu/pub/linux/ALPHA/scsi/scsidev-X.Y.tar.gz

2
Documentation/sound/alsa/Audigy-mixer.txt
View File

@@ -6,7 +6,7 @@ This is based on SB-Live-mixer.txt.
The EMU10K2 chips have a DSP part which can be programmed to support The EMU10K2 chips have a DSP part which can be programmed to support
various ways of sample processing, which is described here. various ways of sample processing, which is described here.
(This acticle does not deal with the overall functionality of the (This article does not deal with the overall functionality of the
EMU10K2 chips. See the manuals section for further details.) EMU10K2 chips. See the manuals section for further details.)
The ALSA driver programs this portion of chip by default code The ALSA driver programs this portion of chip by default code

2
Documentation/sound/alsa/SB-Live-mixer.txt
View File

@@ -5,7 +5,7 @@
The EMU10K1 chips have a DSP part which can be programmed to support The EMU10K1 chips have a DSP part which can be programmed to support
various ways of sample processing, which is described here. various ways of sample processing, which is described here.
(This acticle does not deal with the overall functionality of the (This article does not deal with the overall functionality of the
EMU10K1 chips. See the manuals section for further details.) EMU10K1 chips. See the manuals section for further details.)
The ALSA driver programs this portion of chip by default code The ALSA driver programs this portion of chip by default code

2
Documentation/uml/UserModeLinux-HOWTO.txt
View File

@@ -1477,7 +1477,7 @@
Making it world-writeable looks bad, but it seems not to be Making it world-writable looks bad, but it seems not to be
exploitable as a security hole. However, it does allow anyone to cre- exploitable as a security hole. However, it does allow anyone to cre-
ate useless tap devices (useless because they can't configure them), ate useless tap devices (useless because they can't configure them),
which is a DOS attack. A somewhat more secure alternative would to be which is a DOS attack. A somewhat more secure alternative would to be