diff options
| author | Matt LaPlante <kernel1@cyberdogtech.com> | 2006-10-03 22:54:15 +0200 |
|---|---|---|
| committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 22:54:15 +0200 |
| commit | d6bc8ac9e13e466e844313b590fbc49f7f1abdea (patch) | |
| tree | c7c1ad2057d46d5e878ee034eaa9e4885a67d526 /Documentation/s390 | |
| parent | 84eb8d0608af1576175307ed8fb3c8fde329e579 (diff) | |
Fix typos in Documentation/: 'Q'-'R'
This patch fixes typos in various Documentation txts. The patch addresses
some words starting with the letters 'Q'-'R'.
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/s390')
| -rw-r--r-- | Documentation/s390/cds.txt | 2 | ||||
| -rw-r--r-- | Documentation/s390/driver-model.txt | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/s390/cds.txt b/Documentation/s390/cds.txt index 265a313456e..d80e5733827 100644 --- a/Documentation/s390/cds.txt +++ b/Documentation/s390/cds.txt @@ -133,7 +133,7 @@ determine the device driver owning the device that raised the interrupt. In order not to introduce a new I/O concept to the common Linux code, Linux/390 preserves the IRQ concept and semantically maps the ESA/390 subchannels to Linux as IRQs. This allows Linux/390 to support up to 64k -different IRQs, uniquely representig a single device each. +different IRQs, uniquely representing a single device each. Up to kernel 2.4, Linux/390 used to provide interfaces via the IRQ (subchannel). For internal use of the common I/O layer, these are still there. However, diff --git a/Documentation/s390/driver-model.txt b/Documentation/s390/driver-model.txt index 5295a835d55..62c082387ae 100644 --- a/Documentation/s390/driver-model.txt +++ b/Documentation/s390/driver-model.txt @@ -157,7 +157,7 @@ notify: This function is called by the common I/O layer for some state changes * In online state, device detached (CIO_GONE) or last path gone (CIO_NO_PATH). The driver must return !0 to keep the device; for return code 0, the device will be deleted as usual (also when no - notify function is registerd). If the driver wants to keep the + notify function is registered). If the driver wants to keep the device, it is moved into disconnected state. * In disconnected state, device operational again (CIO_OPER). The common I/O layer performs some sanity checks on device number and |