mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-29 03:01:39 -04:00
Fix typos in Documentation/: 'D'-'E'
This patch fixes typos in various Documentation txts. This patch addresses some words starting with the letters 'D'-'E'. Signed-off-by: Matt LaPlante <[email protected]> Signed-off-by: Adrian Bunk <[email protected]>
This commit is contained in:
parent
6c28f2c0f2
commit
fff9289b21
38 changed files with 63 additions and 64 deletions
|
|
@ -68,7 +68,7 @@ request for an already acquired lock will not generate another DLM
|
|||
call. Userspace programs are assumed to handle their own local
|
||||
locking.
|
||||
|
||||
Two levels of locks are supported - Shared Read, and Exlcusive.
|
||||
Two levels of locks are supported - Shared Read, and Exclusive.
|
||||
Also supported is a Trylock operation.
|
||||
|
||||
For information on the libo2dlm interface, please see o2dlm.h,
|
||||
|
|
|
|||
|
|
@ -390,7 +390,7 @@ stripes with parity, i.e. raid level 5, should not work, too.
|
|||
|
||||
You have to use the "persistent-superblock 0" option for each raid-disk in the
|
||||
NTFS volume/stripe you are configuring in /etc/raidtab as the persistent
|
||||
superblock used by the MD driver would damange the NTFS volume.
|
||||
superblock used by the MD driver would damage the NTFS volume.
|
||||
|
||||
Windows by default uses a stripe chunk size of 64k, so you probably want the
|
||||
"chunk-size 64k" option for each raid-disk, too.
|
||||
|
|
|
|||
|
|
@ -238,7 +238,7 @@ Top Level Directory Layout
|
|||
The sysfs directory arrangement exposes the relationship of kernel
|
||||
data structures.
|
||||
|
||||
The top level sysfs diretory looks like:
|
||||
The top level sysfs directory looks like:
|
||||
|
||||
block/
|
||||
bus/
|
||||
|
|
|
|||
Loading…
Reference in a new issue