aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/s390
diff options
context:
space:
mode:
authorMatt LaPlante <kernel1@cyberdogtech.com>2006-10-03 22:53:09 +0200
committerAdrian Bunk <bunk@stusta.de>2006-10-03 22:53:09 +0200
commit84eb8d0608af1576175307ed8fb3c8fde329e579 (patch)
tree13f3223e6907ebe309328d460fe51ce7ac346ae1 /Documentation/s390
parent992caacf1141b31e94540eb31e0540e3da3a5e25 (diff)
downloadkernel_samsung_smdk4412-84eb8d0608af1576175307ed8fb3c8fde329e579.zip
kernel_samsung_smdk4412-84eb8d0608af1576175307ed8fb3c8fde329e579.tar.gz
kernel_samsung_smdk4412-84eb8d0608af1576175307ed8fb3c8fde329e579.tar.bz2
Fix "can not" in Documentation and Kconfig
Randy brought it to my attention that in proper english "can not" should always be written "cannot". I donot see any reason to argue, even if I mightnot understand why this rule exists. This patch fixes "can not" in several Documentation files as well as three Kconfigs. 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.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/s390/cds.txt b/Documentation/s390/cds.txt
index b2acf4b..265a313 100644
--- a/Documentation/s390/cds.txt
+++ b/Documentation/s390/cds.txt
@@ -143,7 +143,7 @@ During its startup the Linux/390 system checks for peripheral devices. Each
of those devices is uniquely defined by a so called subchannel by the ESA/390
channel subsystem. While the subchannel numbers are system generated, each
subchannel also takes a user defined attribute, the so called device number.
-Both subchannel number and device number can not exceed 65535. During driverfs
+Both subchannel number and device number cannot exceed 65535. During driverfs
initialisation, the information about control unit type and device types that
imply specific I/O commands (channel command words - CCWs) in order to operate
the device are gathered. Device drivers can retrieve this set of hardware