Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

Fix typos in Documentation/: 'N'-'P'

This patch fixes typos in various Documentation txts. The patch addresses
some words starting with the letters 'N'-'P'.

Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Adrian Bunk <bunk@stusta.de>

authored by

Matt LaPlante and committed by
Adrian Bunk
992caacf 2fe0ae78

+78 -79
+1 -1
Documentation/arm/Samsung-S3C24XX/EB2410ITX.txt
··· 38 38 --- 39 39 40 40 The NAND and NOR support has been merged from the linux-mtd project. 41 - Any prolbems, see http://www.linux-mtd.infradead.org/ for more 41 + Any problems, see http://www.linux-mtd.infradead.org/ for more 42 42 information or up-to-date versions of linux-mtd. 43 43 44 44
+2 -2
Documentation/block/as-iosched.txt
··· 99 99 at a time during a write batch. It is this characteristic that can make 100 100 the anticipatory scheduler perform anomalously with controllers supporting 101 101 TCQ, or with hardware striped RAID devices. Setting the antic_expire 102 - queue paramter (see below) to zero disables this behavior, and the anticipatory 103 - scheduler behaves essentially like the deadline scheduler. 102 + queue parameter (see below) to zero disables this behavior, and the 103 + anticipatory scheduler behaves essentially like the deadline scheduler. 104 104 105 105 When read anticipation is enabled (antic_expire is not zero), reads 106 106 are dispatched to the disk controller one at a time.
+1 -1
Documentation/block/barrier.txt
··· 42 42 of ii. Just keeping issue order suffices. Ancient SCSI 43 43 controllers/drives and IDE drives are in this category. 44 44 45 - 2. Forced flushing to physcial medium 45 + 2. Forced flushing to physical medium 46 46 47 47 Again, if you're not gonna do synchronization with disk drives (dang, 48 48 it sounds even more appealing now!), the reason you use I/O barriers
+4 -4
Documentation/cpu-freq/governors.txt
··· 137 137 If set to '1' then the frequency decreases as quickly as it increases, 138 138 if set to '2' it decreases at half the rate of the increase. 139 139 140 - ignore_nice_load: this parameter takes a value of '0' or '1', when set 141 - to '0' (its default) then all processes are counted towards towards the 142 - 'cpu utilisation' value. When set to '1' then processes that are 140 + ignore_nice_load: this parameter takes a value of '0' or '1'. When 141 + set to '0' (its default), all processes are counted towards the 142 + 'cpu utilisation' value. When set to '1', the processes that are 143 143 run with a 'nice' value will not count (and thus be ignored) in the 144 - overal usage calculation. This is useful if you are running a CPU 144 + overall usage calculation. This is useful if you are running a CPU 145 145 intensive calculation on your laptop that you do not care how long it 146 146 takes to complete as you can 'nice' it and prevent it from taking part 147 147 in the deciding process of whether to increase your CPU frequency.
+5 -5
Documentation/dell_rbu.txt
··· 52 52 In packet update mode the packet size has to be given before any packets can 53 53 be downloaded. It is done as below 54 54 echo XXXX > /sys/devices/platform/dell_rbu/packet_size 55 - In the packet update mechanism, the user neesd to create a new file having 55 + In the packet update mechanism, the user needs to create a new file having 56 56 packets of data arranged back to back. It can be done as follows 57 57 The user creates packets header, gets the chunk of the BIOS image and 58 58 places it next to the packetheader; now, the packetheader + BIOS image chunk ··· 93 93 NOTE: 94 94 This driver requires a patch for firmware_class.c which has the modified 95 95 request_firmware_nowait function. 96 - Also after updating the BIOS image an user mdoe application neeeds to execute 97 - code which message the BIOS update request to the BIOS. So on the next reboot 98 - the BIOS knows about the new image downloaded and it updates it self. 99 - Also don't unload the rbu drive if the image has to be updated. 96 + Also after updating the BIOS image a user mode application needs to execute 97 + code which sends the BIOS update request to the BIOS. So on the next reboot 98 + the BIOS knows about the new image downloaded and it updates itself. 99 + Also don't unload the rbu driver if the image has to be updated. 100 100
+2 -2
Documentation/devices.txt
··· 2005 2005 116 char Advanced Linux Sound Driver (ALSA) 2006 2006 2007 2007 116 block MicroMemory battery backed RAM adapter (NVRAM) 2008 - Supports 16 boards, 15 paritions each. 2008 + Supports 16 boards, 15 partitions each. 2009 2009 Requested by neilb at cse.unsw.edu.au. 2010 2010 2011 2011 0 = /dev/umem/d0 Whole of first board ··· 3094 3094 This major is reserved to assist the expansion to a 3095 3095 larger number space. No device nodes with this major 3096 3096 should ever be created on the filesystem. 3097 - (This is probaly not true anymore, but I'll leave it 3097 + (This is probably not true anymore, but I'll leave it 3098 3098 for now /Torben) 3099 3099 3100 3100 ---LARGE MAJORS!!!!!---
+2 -2
Documentation/dvb/avermedia.txt
··· 45 45 by circuitry on the card and is often presented uncompressed. 46 46 For a PAL TV signal encoded at a resolution of 768x576 24-bit 47 47 color pixels over 25 frames per second - a fair amount of data 48 - is generated and must be proceesed by the PC before it can be 48 + is generated and must be processed by the PC before it can be 49 49 displayed on the video monitor screen. Some Analogue TV cards 50 - for PC's have onboard MPEG2 encoders which permit the raw 50 + for PCs have onboard MPEG2 encoders which permit the raw 51 51 digital data stream to be presented to the PC in an encoded 52 52 and compressed form - similar to the form that is used in 53 53 Digital TV.
+1 -1
Documentation/dvb/faq.txt
··· 5 5 It's not a bug, it's a feature. Because the frontends have 6 6 significant power requirements (and hence get very hot), they 7 7 are powered down if they are unused (i.e. if the frontend device 8 - is closed). The dvb-core.o module paramter "dvb_shutdown_timeout" 8 + is closed). The dvb-core.o module parameter "dvb_shutdown_timeout" 9 9 allow you to change the timeout (default 5 seconds). Setting the 10 10 timeout to 0 disables the timeout feature. 11 11
+1 -1
Documentation/eisa.txt
··· 84 84 85 85 id_table : an array of NULL terminated EISA id strings, 86 86 followed by an empty string. Each string can 87 - optionnaly be paired with a driver-dependant value 87 + optionally be paired with a driver-dependant value 88 88 (driver_data). 89 89 90 90 driver : a generic driver, such as described in
+2 -2
Documentation/fb/sstfb.txt
··· 72 72 73 73 Kernel/Modules Options 74 74 75 - You can pass some otions to sstfb module, and via the kernel command 76 - line when the driver is compiled in : 75 + You can pass some options to the sstfb module, and via the kernel 76 + command line when the driver is compiled in: 77 77 for module : insmod sstfb.o option1=value1 option2=value2 ... 78 78 in kernel : video=sstfb:option1,option2:value2,option3 ... 79 79
+2 -2
Documentation/filesystems/befs.txt
··· 22 22 details. 23 23 24 24 Original Author: Makoto Kato <m_kato@ga2.so-net.ne.jp> 25 - His orriginal code can still be found at: 25 + His original code can still be found at: 26 26 <http://hp.vector.co.jp/authors/VA008030/bfs/> 27 27 Does anyone know of a more current email address for Makoto? He doesn't 28 28 respond to the address given above... ··· 39 39 ================ 40 40 Be, Inc said, "BeOS Filesystem is officially called BFS, not BeFS". 41 41 But Unixware Boot Filesystem is called bfs, too. And they are already in 42 - the kernel. Because of this nameing conflict, on Linux the BeOS 42 + the kernel. Because of this naming conflict, on Linux the BeOS 43 43 filesystem is called befs. 44 44 45 45 HOW TO INSTALL
+1 -1
Documentation/filesystems/ext2.txt
··· 205 205 206 206 In ext2, there is a mechanism for reserving a certain number of blocks 207 207 for a particular user (normally the super-user). This is intended to 208 - allow for the system to continue functioning even if non-priveleged users 208 + allow for the system to continue functioning even if non-privileged users 209 209 fill up all the space available to them (this is independent of filesystem 210 210 quotas). It also keeps the filesystem from filling up entirely which 211 211 helps combat fragmentation.
+1 -1
Documentation/filesystems/spufs.txt
··· 359 359 EFAULT npc is not a valid pointer or status is neither NULL nor a valid 360 360 pointer. 361 361 362 - EINTR A signal occured while spu_run was in progress. The npc value 362 + EINTR A signal occurred while spu_run was in progress. The npc value 363 363 has been updated to the new program counter value if necessary. 364 364 365 365 EINVAL fd is not a file descriptor returned from spu_create(2).
+1 -1
Documentation/hrtimers.txt
··· 27 27 high-res timers. 28 28 29 29 - the unpredictable [O(N)] overhead of cascading leads to delays which 30 - necessiate a more complex handling of high resolution timers, which 30 + necessitate a more complex handling of high resolution timers, which 31 31 in turn decreases robustness. Such a design still led to rather large 32 32 timing inaccuracies. Cascading is a fundamental property of the timer 33 33 wheel concept, it cannot be 'designed out' without unevitably
+2 -2
Documentation/input/joystick-parport.txt
··· 465 465 466 466 There are two options specific to PSX driver portion. gamecon.psx_delay sets 467 467 the command delay when talking to the controllers. The default of 25 should 468 - work but you can try lowering it for better performace. If your pads don't 469 - respond try raising it untill they work. Setting the type to 8 allows the 468 + work but you can try lowering it for better performance. If your pads don't 469 + respond try raising it until they work. Setting the type to 8 allows the 470 470 driver to be used with Dance Dance Revolution or similar games. Arrow keys are 471 471 registered as key presses instead of X and Y axes. 472 472
+1 -1
Documentation/lockdep-design.txt
··· 170 170 171 171 The validator achieves perfect, mathematical 'closure' (proof of locking 172 172 correctness) in the sense that for every simple, standalone single-task 173 - locking sequence that occured at least once during the lifetime of the 173 + locking sequence that occurred at least once during the lifetime of the 174 174 kernel, the validator proves it with a 100% certainty that no 175 175 combination and timing of these locking sequences can cause any class of 176 176 lock related deadlock. [*]
+2 -2
Documentation/md.txt
··· 330 330 This gives the role that the device has in the array. It will 331 331 either be 'none' if the device is not active in the array 332 332 (i.e. is a spare or has failed) or an integer less than the 333 - 'raid_disks' number for the array indicating which possition 333 + 'raid_disks' number for the array indicating which position 334 334 it currently fills. This can only be set while assembling an 335 335 array. A device for which this is set is assumed to be working. 336 336 ··· 353 353 354 354 rdNN 355 355 356 - where 'NN' is the possition in the array, starting from 0. 356 + where 'NN' is the position in the array, starting from 0. 357 357 So for a 3 drive array there will be rd0, rd1, rd2. 358 358 These are symbolic links to the appropriate 'dev-XXX' entry. 359 359 Thus, for example,
+2 -2
Documentation/networking/gen_stats.txt
··· 79 79 80 80 0) Prepare an estimator attribute. Most likely this would be in user 81 81 space. The value of this TLV should contain a tc_estimator structure. 82 - As usual, such a TLV nees to be 32 bit aligned and therefore the 83 - length needs to be appropriately set etc. The estimator interval 82 + As usual, such a TLV needs to be 32 bit aligned and therefore the 83 + length needs to be appropriately set, etc. The estimator interval 84 84 and ewma log need to be converted to the appropriate values. 85 85 tc_estimator.c::tc_setup_estimator() is advisable to be used as the 86 86 conversion routine. It does a few clever things. It takes a time
+1 -1
Documentation/networking/packet_mmap.txt
··· 278 278 All memory allocations are not freed until the socket is closed. The memory 279 279 allocations are done with GFP_KERNEL priority, this basically means that 280 280 the allocation can wait and swap other process' memory in order to allocate 281 - the nececessary memory, so normally limits can be reached. 281 + the necessary memory, so normally limits can be reached. 282 282 283 283 Other constraints 284 284 -------------------
+4 -4
Documentation/networking/sk98lin.txt
··· 180 180 1. Insert a line of the form : 181 181 options sk98lin ... 182 182 For "...", the same syntax is required as described for the command 183 - line paramaters of modprobe below. 183 + line parameters of modprobe below. 184 184 2. To activate the new parameters, either reboot your computer 185 185 or 186 186 unload and reload the driver. ··· 364 364 Values: 30...40000 (interrupts per second) 365 365 Default: 2000 366 366 367 - This parameter is only used, if either static or dynamic interrupt moderation 368 - is used on a network adapter card. Using this paramter if no moderation is 369 - applied, will lead to no action performed. 367 + This parameter is only used if either static or dynamic interrupt moderation 368 + is used on a network adapter card. Using this parameter if no moderation is 369 + applied will lead to no action performed. 370 370 371 371 This parameter determines the length of any interrupt moderation interval. 372 372 Assuming that static interrupt moderation is to be used, an 'IntsPerSec'
+2 -2
Documentation/networking/vortex.txt
··· 359 359 360 360 Eliminate some variables: try different cards, different 361 361 computers, different cables, different ports on the switch/hub, 362 - different versions of the kernel or ofthe driver, etc. 362 + different versions of the kernel or of the driver, etc. 363 363 364 364 - OK, it's a driver problem. 365 365 366 366 You need to generate a report. Typically this is an email to the 367 367 maintainer and/or linux-net@vger.kernel.org. The maintainer's 368 - email address will be inthe driver source or in the MAINTAINERS file. 368 + email address will be in the driver source or in the MAINTAINERS file. 369 369 370 370 - The contents of your report will vary a lot depending upon the 371 371 problem. If it's a kernel crash then you should refer to the
+4 -4
Documentation/networking/wan-router.txt
··· 214 214 /usr/local/wanrouter/patches/kdrivers: 215 215 Sources of the latest WANPIPE device drivers. 216 216 These are used to UPGRADE the linux kernel to the newest 217 - version if the kernel source has already been pathced with 217 + version if the kernel source has already been patched with 218 218 WANPIPE drivers. 219 219 220 220 /usr/local/wanrouter/samples: ··· 438 438 2.2.X kernels only 439 439 440 440 o Secured the driver UDP debugging calls 441 - - All illegal netowrk debugging calls are reported to 441 + - All illegal network debugging calls are reported to 442 442 the log. 443 443 - Defined a set of allowed commands, all other denied. 444 444 ··· 451 451 452 452 o Keyboard Led Monitor/Debugger 453 453 - A new utilty /usr/sbin/wpkbdmon uses keyboard leds 454 - to convey operatinal statistic information of the 454 + to convey operational statistic information of the 455 455 Sangoma WANPIPE cards. 456 456 NUM_LOCK = Line State (On=connected, Off=disconnected) 457 457 CAPS_LOCK = Tx data (On=transmitting, Off=no tx data) ··· 470 470 o Fixed the Frame Relay and Chdlc network interfaces so they are 471 471 compatible with libpcap libraries. Meaning, tcpdump, snort, 472 472 ethereal, and all other packet sniffers and debuggers work on 473 - all WANPIPE netowrk interfaces. 473 + all WANPIPE network interfaces. 474 474 - Set the network interface encoding type to ARPHRD_PPP. 475 475 This tell the sniffers that data obtained from the 476 476 network interface is in pure IP format.
+1 -1
Documentation/power/userland-swsusp.txt
··· 91 91 still frozen when the device is being closed). 92 92 93 93 Currently it is assumed that the userland utilities reading/writing the 94 - snapshot image from/to the kernel will use a swap parition, called the resume 94 + snapshot image from/to the kernel will use a swap partition, called the resume 95 95 partition, as storage space. However, this is not really required, as they 96 96 can use, for example, a special (blank) suspend partition or a file on a partition 97 97 that is unmounted before SNAPSHOT_ATOMIC_SNAPSHOT and mounted afterwards.
+1 -1
Documentation/power/video.txt
··· 16 16 that. 17 17 18 18 We either have to run video BIOS during early resume, or interpret it 19 - using vbetool later, or maybe nothing is neccessary on particular 19 + using vbetool later, or maybe nothing is necessary on particular 20 20 system because video state is preserved. Unfortunately different 21 21 methods work on different systems, and no known method suits all of 22 22 them.
+2 -3
Documentation/powerpc/booting-without-of.txt
··· 630 630 prom_parse.c file of the recent kernels for your bus type. 631 631 632 632 The "reg" property only defines addresses and sizes (if #size-cells 633 - is 634 - non-0) within a given bus. In order to translate addresses upward 633 + is non-0) within a given bus. In order to translate addresses upward 635 634 (that is into parent bus addresses, and possibly into cpu physical 636 635 addresses), all busses must contain a "ranges" property. If the 637 636 "ranges" property is missing at a given level, it's assumed that 638 - translation isn't possible. The format of the "ranges" proprety for a 637 + translation isn't possible. The format of the "ranges" property for a 639 638 bus is a list of: 640 639 641 640 bus address, parent bus address, size
+8 -8
Documentation/s390/Debugging390.txt
··· 366 366 Overview: 367 367 --------- 368 368 This is the code that gcc produces at the top & the bottom of 369 - each function, it usually is fairly consistent & similar from 370 - function to function & if you know its layout you can probalby 369 + each function. It usually is fairly consistent & similar from 370 + function to function & if you know its layout you can probably 371 371 make some headway in finding the ultimate cause of a problem 372 372 after a crash without a source level debugger. 373 373 ··· 1703 1703 IOP's can use one or more links ( known as channel paths ) to talk to each 1704 1704 IO device. It first checks for path availability & chooses an available one, 1705 1705 then starts ( & sometimes terminates IO ). 1706 - There are two types of channel path ESCON & the Paralell IO interface. 1706 + There are two types of channel path: ESCON & the Parallel IO interface. 1707 1707 1708 1708 IO devices are attached to control units, control units provide the 1709 1709 logic to interface the channel paths & channel path IO protocols to ··· 1742 1742 1743 1743 The 390 IO systems come in 2 flavours the current 390 machines support both 1744 1744 1745 - The Older 360 & 370 Interface,sometimes called the paralell I/O interface, 1745 + The Older 360 & 370 Interface,sometimes called the Parallel I/O interface, 1746 1746 sometimes called Bus-and Tag & sometimes Original Equipment Manufacturers 1747 1747 Interface (OEMI). 1748 1748 1749 - This byte wide paralell channel path/bus has parity & data on the "Bus" cable 1749 + This byte wide Parallel channel path/bus has parity & data on the "Bus" cable 1750 1750 & control lines on the "Tag" cable. These can operate in byte multiplex mode for 1751 1751 sharing between several slow devices or burst mode & monopolize the channel for the 1752 1752 whole burst. Upto 256 devices can be addressed on one of these cables. These cables are ··· 1776 1776 DASD's direct access storage devices ( otherwise known as hard disks ). 1777 1777 Tape Drives. 1778 1778 CTC ( Channel to Channel Adapters ), 1779 - ESCON or Paralell Cables used as a very high speed serial link 1779 + ESCON or Parallel Cables used as a very high speed serial link 1780 1780 between 2 machines. We use 2 cables under linux to do a bi-directional serial link. 1781 1781 1782 1782 ··· 1802 1802 OSA 7C14 ON OSA 7C14 SUBCHANNEL = 0002 1803 1803 OSA 7C15 ON OSA 7C15 SUBCHANNEL = 0003 1804 1804 1805 - If you have a guest with certain priviliges you may be able to see devices 1806 - which don't belong to you to avoid this do add the option V. 1805 + If you have a guest with certain privileges you may be able to see devices 1806 + which don't belong to you. To avoid this, add the option V. 1807 1807 e.g. 1808 1808 Q V OSA 1809 1809
+2 -2
Documentation/s390/cds.txt
··· 177 177 The function is meant to be called with an irq handler in place; that is, 178 178 at earliest during set_online() processing. 179 179 180 - While the request is procesed synchronously, the device interrupt 180 + While the request is processed synchronously, the device interrupt 181 181 handler is called for final ending status. In case of error situations the 182 182 interrupt handler may recover appropriately. The device irq handler can 183 183 recognize the corresponding interrupts by the interruption parameter be 184 - 0x00524443.The ccw_device must not be locked prior to calling read_dev_chars(). 184 + 0x00524443. The ccw_device must not be locked prior to calling read_dev_chars(). 185 185 186 186 The function may be called enabled or disabled. 187 187
+2 -2
Documentation/s390/crypto/crypto-API.txt
··· 61 61 -> when the sha1 algorithm is requested through the crypto API 62 62 (which has a module autoloader) the z990 module will be loaded. 63 63 64 - TBD: a userspace module probin mechanism 64 + TBD: a userspace module probing mechanism 65 65 something like 'probe sha1 sha1_z990 sha1' in modprobe.conf 66 - -> try module sha1_z990, if it fails to load load standard module sha1 66 + -> try module sha1_z990, if it fails to load standard module sha1 67 67 the 'probe' statement is currently not supported in modprobe.conf 68 68 69 69
+2 -2
Documentation/s390/s390dbf.txt
··· 83 83 It is also possible to deactivate the debug feature globally for every 84 84 debug log. You can change the behavior using 2 sysctl parameters in 85 85 /proc/sys/s390dbf: 86 - There are currently 2 possible triggers, which stop the debug feature 87 - globally. The first possbility is to use the "debug_active" sysctl. If 86 + There are currently 2 possible triggers, which stop the debug feature 87 + globally. The first possibility is to use the "debug_active" sysctl. If 88 88 set to 1 the debug feature is running. If "debug_active" is set to 0 the 89 89 debug feature is turned off. 90 90 The second trigger which stops the debug feature is an kernel oops.
+2 -2
Documentation/scsi/NinjaSCSI.txt
··· 59 59 ... 60 60 $ make 61 61 62 - [5] Copy nsp_cs.o to suitable plase, like /lib/modules/<Kernel version>/pcmcia/ . 62 + [5] Copy nsp_cs.ko to suitable place, like /lib/modules/<Kernel version>/pcmcia/ . 63 63 64 64 [6] Add these lines to /etc/pcmcia/config . 65 - If you yse pcmcia-cs-3.1.8 or later, we can use "nsp_cs.conf" file. 65 + If you use pcmcia-cs-3.1.8 or later, we can use "nsp_cs.conf" file. 66 66 So, you don't need to edit file. Just copy to /etc/pcmcia/ . 67 67 68 68 -------------------------------------
+1 -1
Documentation/scsi/aic79xx.txt
··· 94 94 - Add support for scsi_report_device_reset() found in 95 95 2.5.X kernels. 96 96 - Add 7901B support. 97 - - Simplify handling of the packtized lun Rev A workaround. 97 + - Simplify handling of the packetized lun Rev A workaround. 98 98 - Correct and simplify handling of the ignore wide residue 99 99 message. The previous code would fail to report a residual 100 100 if the transaction data length was even and we received
+1 -1
Documentation/scsi/dc395x.txt
··· 20 20 ---------- 21 21 The driver uses the settings from the EEPROM set in the SCSI BIOS 22 22 setup. If there is no EEPROM, the driver uses default values. 23 - Both can be overriden by command line parameters (module or kernel 23 + Both can be overridden by command line parameters (module or kernel 24 24 parameters). 25 25 26 26 The following parameters are available:
+1 -1
Documentation/scsi/ibmmca.txt
··· 1086 1086 1087 1087 Q: "Reset SCSI-devices at boottime" halts the system at boottime, why? 1088 1088 A: This is only tested with the IBM SCSI Adapter w/cache. It is not 1089 - yet prooved to run on other adapters, however you may be lucky. 1089 + yet proven to run on other adapters, however you may be lucky. 1090 1090 In version 3.1d this has been hugely improved and should work better, 1091 1091 now. Normally you really won't need to activate this flag in the 1092 1092 kernel configuration, as all post 1989 SCSI-devices should accept
+3 -3
Documentation/scsi/ncr53c8xx.txt
··· 631 631 632 632 A boot setup command for the ncr53c8xx (sym53c8xx) driver begins with the 633 633 driver name "ncr53c8xx="(sym53c8xx). The kernel syntax parser then expects 634 - an optionnal list of integers separated with comma followed by an optional 635 - list of comma-separated strings. Example of boot setup command under lilo 634 + an optional list of integers separated with comma followed by an optional 635 + list of comma-separated strings. Example of boot setup command under lilo 636 636 prompt: 637 637 638 638 lilo: linux root=/dev/hda2 ncr53c8xx=tags:4,sync:10,debug:0x200 ··· 899 899 ncr53c8xx=safe:y,mpar:y 900 900 ncr53c8xx=safe:y 901 901 902 - My personnal system works flawlessly with the following equivalent setup: 902 + My personal system works flawlessly with the following equivalent setup: 903 903 904 904 ncr53c8xx=mpar:y,spar:y,disc:y,specf:1,fsn:n,ultra:2,fsn:n,revprob:n,verb:1\ 905 905 tags:32,sync:12,debug:0,burst:7,led:1,wide:1,settle:2,diff:0,irqm:0
+1 -1
Documentation/scsi/scsi-changer.txt
··· 31 31 media transport - this one shuffles around the media, i.e. the 32 32 transport arm. Also known as "picker". 33 33 storage - a slot which can hold a media. 34 - import/export - the same as above, but is accessable from outside, 34 + import/export - the same as above, but is accessible from outside, 35 35 i.e. there the operator (you !) can use this to 36 36 fill in and remove media from the changer. 37 37 Sometimes named "mailslot".
+1 -1
Documentation/sound/alsa/CMIPCI.txt
··· 76 76 77 77 % aplay -Dsurround51 sixchannels.wav 78 78 79 - For programmin the 4/6 channel playback, you need to specify the PCM 79 + For programming the 4/6 channel playback, you need to specify the PCM 80 80 channels as you like and set the format S16LE. For example, for playback 81 81 with 4 channels, 82 82
+2 -2
Documentation/sparc/sbus_drivers.txt
··· 25 25 used members of this structure, and their typical usage, 26 26 will be detailed below. 27 27 28 - Here is a piece of skeleton code for perofming a device 29 - probe in an SBUS driverunder Linux: 28 + Here is a piece of skeleton code for performing a device 29 + probe in an SBUS driver under Linux: 30 30 31 31 static int __devinit mydevice_probe_one(struct sbus_dev *sdev) 32 32 {
+1 -1
Documentation/uml/UserModeLinux-HOWTO.txt
··· 2031 2031 there are multiple COWs associated with a backing file, a -d merge of 2032 2032 one of them will invalidate all of the others. However, it is 2033 2033 convenient if you're short of disk space, and it should also be 2034 - noticably faster than a non-destructive merge. 2034 + noticeably faster than a non-destructive merge. 2035 2035 2036 2036 2037 2037
+1 -1
Documentation/usb/usb-serial.txt
··· 272 272 work under SMP with the uhci driver. 273 273 274 274 The driver is generally working, though we still have a few more ioctls 275 - to implement and final testing and debugging to do. The paralled port 275 + to implement and final testing and debugging to do. The parallel port 276 276 on the USB 2 is supported as a serial to parallel converter; in other 277 277 words, it appears as another USB serial port on Linux, even though 278 278 physically it is really a parallel port. The Digi Acceleport USB 8
+1 -1
Documentation/video4linux/cx2341x/fw-encoder-api.txt
··· 280 280 Param[1] 281 281 Unknown, but leaving this to 0 seems to work best. Indications are that 282 282 this might have to do with USB support, although passing anything but 0 283 - onl breaks things. 283 + only breaks things. 284 284 285 285 ------------------------------------------------------------------------------- 286 286
+1 -1
Documentation/video4linux/w9968cf.txt
··· 15 15 5. Supported devices 16 16 6. Module dependencies 17 17 7. Module loading 18 - 8. Module paramaters 18 + 8. Module parameters 19 19 9. Contact information 20 20 10. Credits 21 21