Documentation/s390/DASD:17: ERROR: trailing whitespace
Documentation/s390/DASD:24: ERROR: trailing whitespace
Documentation/s390/DASD:44: ERROR: trailing whitespace
Documentation/s390/DASD:62: ERROR: trailing whitespace
Signed-off-by: Andrea Gelmini <andrea.gelmini@xxxxxxxxx>
---
Documentation/s390/DASD | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/s390/DASD b/Documentation/s390/DASD
index 9963f1e..9e3e849 100644
--- a/Documentation/s390/DASD
+++ b/Documentation/s390/DASD
@@ -14,14 +14,14 @@ parameters are to be given in hexadecimal notation without a leading
If you supply kernel parameters the different instances are processed
in order of appearance and a minor number is reserved for any device
covered by the supplied range up to 64 volumes. Additional DASDs are
-ignored. If you do not supply the 'dasd=' kernel parameter at all, the
+ignored. If you do not supply the 'dasd=' kernel parameter at all, the
DASD driver registers all supported DASDs of your system to a minor
number in ascending order of the subchannel number.
The driver currently supports ECKD-devices and there are stubs for
support of the FBA and CKD architectures. For the FBA architecture
only some smart data structures are missing to make the support
-complete.
+complete.
We performed our testing on 3380 and 3390 type disks of different
sizes, under VM and on the bare hardware (LPAR), using internal disks
of the multiprise as well as a RAMAC virtual array. Disks exported by
@@ -41,7 +41,7 @@ For using an ECKD-DASD as a Linux harddisk you have to low-level
format the tracks by issuing the BLKDASDFORMAT-ioctl on that
device. This will erase any data on that volume including IBM volume
labels, VTOCs etc. The ioctl may take a 'struct format_data *' or
-'NULL' as an argument.
+'NULL' as an argument.
typedef struct {
int start_unit;
int stop_unit;
@@ -59,7 +59,7 @@ blksize from 512 byte to 1kB.
-Make a filesystem
Then you can mk??fs the filesystem of your choice on that volume or
partition. For reasons of sanity you should build your filesystem on
-the partition /dev/dd?1 instead of the whole volume. You only lose 3kB
+the partition /dev/dd?1 instead of the whole volume. You only lose 3kB
but may be sure that you can reuse your data after introduction of a
real partition table.
--
1.7.1.251.gf80a2
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
