summaryrefslogtreecommitdiffstats
path: root/Documentation/lockdep-design.txt
diff options
context:
space:
mode:
authorMatt LaPlante <kernel1@cyberdogtech.com>2006-10-03 22:50:39 +0200
committerAdrian Bunk <bunk@stusta.de>2006-10-03 22:50:39 +0200
commit2fe0ae78c6975d6fa2fc0c84f2b8944543054105 (patch)
tree005a185c1043f5b99f4cd851ad071d6e95025064 /Documentation/lockdep-design.txt
parenta2ffd2751683f4275d4d1aa5ce37e5a6a1ae21df (diff)
downloadblackbird-op-linux-2fe0ae78c6975d6fa2fc0c84f2b8944543054105.tar.gz
blackbird-op-linux-2fe0ae78c6975d6fa2fc0c84f2b8944543054105.zip
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/lockdep-design.txt')
-rw-r--r--Documentation/lockdep-design.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/lockdep-design.txt b/Documentation/lockdep-design.txt
index 7f2bb8e342fa..2a76a4af598c 100644
--- a/Documentation/lockdep-design.txt
+++ b/Documentation/lockdep-design.txt
@@ -133,7 +133,7 @@ cases there is an inherent "natural" ordering between the two objects
(defined by the properties of the hierarchy), and the kernel grabs the
locks in this fixed order on each of the objects.
-An example of such an object hieararchy that results in "nested locking"
+An example of such an object hierarchy that results in "nested locking"
is that of a "whole disk" block-dev object and a "partition" block-dev
object; the partition is "part of" the whole device and as long as one
always takes the whole disk lock as a higher lock than the partition
@@ -162,7 +162,7 @@ The validator treats a lock that is taken in such a nested fashion as a
separate (sub)class for the purposes of validation.
Note: When changing code to use the _nested() primitives, be careful and
-check really thoroughly that the hiearchy is correctly mapped; otherwise
+check really thoroughly that the hierarchy is correctly mapped; otherwise
you can get false positives or false negatives.
Proof of 100% correctness:
OpenPOWER on IntegriCloud