diff options
author | Matt LaPlante <kernel1@cyberdogtech.com> | 2006-10-03 22:50:39 +0200 |
---|---|---|
committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 22:50:39 +0200 |
commit | 2fe0ae78c6975d6fa2fc0c84f2b8944543054105 (patch) | |
tree | 005a185c1043f5b99f4cd851ad071d6e95025064 /Documentation/scsi | |
parent | a2ffd2751683f4275d4d1aa5ce37e5a6a1ae21df (diff) | |
download | linux-2fe0ae78c6975d6fa2fc0c84f2b8944543054105.tar.bz2 |
Fix typos in Documentation/: 'H'-'M'
This patch fixes typos in various Documentation txts. The patch addresses
some words starting with the letters 'H'-'M'.
Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/scsi')
-rw-r--r-- | Documentation/scsi/NinjaSCSI.txt | 2 | ||||
-rw-r--r-- | Documentation/scsi/ibmmca.txt | 10 | ||||
-rw-r--r-- | Documentation/scsi/megaraid.txt | 4 | ||||
-rw-r--r-- | Documentation/scsi/ncr53c8xx.txt | 2 | ||||
-rw-r--r-- | Documentation/scsi/scsi_eh.txt | 2 | ||||
-rw-r--r-- | Documentation/scsi/sym53c8xx_2.txt | 2 |
6 files changed, 11 insertions, 11 deletions
diff --git a/Documentation/scsi/NinjaSCSI.txt b/Documentation/scsi/NinjaSCSI.txt index 041780f428ac..17dd54786d37 100644 --- a/Documentation/scsi/NinjaSCSI.txt +++ b/Documentation/scsi/NinjaSCSI.txt @@ -24,7 +24,7 @@ SCSI device: I-O data CDPS-PX24 (CD-ROM drive) You can also use "cardctl" program (this program is in pcmcia-cs source code) to get more info. -# cat /var/log/messgaes +# cat /var/log/messages ... Jan 2 03:45:06 lindberg cardmgr[78]: unsupported card in socket 1 Jan 2 03:45:06 lindberg cardmgr[78]: product info: "WBT", "NinjaSCSI-3", "R1.0" diff --git a/Documentation/scsi/ibmmca.txt b/Documentation/scsi/ibmmca.txt index d16ce5b540f4..a783635b9a8e 100644 --- a/Documentation/scsi/ibmmca.txt +++ b/Documentation/scsi/ibmmca.txt @@ -229,7 +229,7 @@ In a second step of the driver development, the following improvement has been applied: The first approach limited the number of devices to 7, far - fewer than the 15 that it could usem then it just maped ldn -> + fewer than the 15 that it could use, then it just mapped ldn -> (ldn/8,ldn%8) for pun,lun. We ended up with a real mishmash of puns and luns, but it all seemed to work. @@ -254,12 +254,12 @@ device to be existant, but it has no ldn assigned, it gets a ldn out of 7 to 14. The numbers are assigned in cyclic order. Therefore it takes 8 dynamical reassignments on the SCSI-devices, until a certain device - loses its ldn again. This assures, that dynamical remapping is avoided + loses its ldn again. This assures that dynamical remapping is avoided during intense I/O between up to 15 SCSI-devices (means pun,lun - combinations). A further advantage of this method is, that people who + combinations). A further advantage of this method is that people who build their kernel without probing on all luns will get what they expect, because the driver just won't assign everything with lun>0 when - multpile lun probing is inactive. + multiple lun probing is inactive. 2.4 SCSI-Device Order --------------------- @@ -1104,7 +1104,7 @@ The parameter 'normal' sets the new industry standard, starting from pun 0, scanning up to pun 6. This allows you to change your opinion still after having already compiled the kernel. - Q: Why I cannot find the IBM MCA SCSI support in the config menue? + Q: Why can't I find IBM MCA SCSI support in the config menu? A: You have to activate MCA bus support, first. Q: Where can I find the latest info about this driver? A: See the file MAINTAINERS for the current WWW-address, which offers diff --git a/Documentation/scsi/megaraid.txt b/Documentation/scsi/megaraid.txt index ff864c0f494c..3c7cea51e687 100644 --- a/Documentation/scsi/megaraid.txt +++ b/Documentation/scsi/megaraid.txt @@ -4,11 +4,11 @@ Overview: -------- -Different classes of controllers from LSI Logic, accept and respond to the +Different classes of controllers from LSI Logic accept and respond to the user applications in a similar way. They understand the same firmware control commands. Furthermore, the applications also can treat different classes of the controllers uniformly. Hence it is logical to have a single module that -interefaces with the applications on one side and all the low level drivers +interfaces with the applications on one side and all the low level drivers on the other. The advantages, though obvious, are listed for completeness: diff --git a/Documentation/scsi/ncr53c8xx.txt b/Documentation/scsi/ncr53c8xx.txt index e80a02cffb22..29cbbb64e1ce 100644 --- a/Documentation/scsi/ncr53c8xx.txt +++ b/Documentation/scsi/ncr53c8xx.txt @@ -778,7 +778,7 @@ port address 0x1400. Some scsi boards use a 875 (ultra wide) and only supply narrow connectors. If you have connected a wide device with a 50 pins to 68 pins cable converter, any accepted wide negotiation will break further data transfers. - In such a case, using "wide:0" in the bootup command will be helpfull. + In such a case, using "wide:0" in the bootup command will be helpful. 10.2.14 Differential mode diff:0 never set up diff mode diff --git a/Documentation/scsi/scsi_eh.txt b/Documentation/scsi/scsi_eh.txt index 8d6253f9cb32..b964eef2f62f 100644 --- a/Documentation/scsi/scsi_eh.txt +++ b/Documentation/scsi/scsi_eh.txt @@ -194,7 +194,7 @@ lower layers and lower layers are ready to process or fail the scmd again. To achieve these goals, EH performs recovery actions with increasing -severity. Some actions are performed by issueing SCSI commands and +severity. Some actions are performed by issuing SCSI commands and others are performed by invoking one of the following fine-grained hostt EH callbacks. Callbacks may be omitted and omitted ones are considered to fail always. diff --git a/Documentation/scsi/sym53c8xx_2.txt b/Documentation/scsi/sym53c8xx_2.txt index 7f516cdcd262..98d5f1ec124f 100644 --- a/Documentation/scsi/sym53c8xx_2.txt +++ b/Documentation/scsi/sym53c8xx_2.txt @@ -684,7 +684,7 @@ Field H : SCNTL3 Scsi Control Register 3 Contains the setting of timing values for both asynchronous and synchronous data transfers. Field I : SCNTL4 Scsi Control Register 4 - Only meaninful for 53C1010 Ultra3 controllers. + Only meaningful for 53C1010 Ultra3 controllers. Understanding Fields J, K, L and dumps requires to have good knowledge of SCSI standards, chip cores functionnals and internal driver data structures. |