summaryrefslogtreecommitdiff
path: root/Documentation/DocBook/kernel-locking.tmpl
diff options
context:
space:
mode:
authorMasanari Iida <standby24x7@gmail.com>2014-07-12 09:55:28 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2014-07-12 11:30:36 -0700
commit0ba4f6e4006634cf566ba9cc3acd40aebee44503 (patch)
treefb6ec3a4bd782dcab7beab39e749626038a9683d /Documentation/DocBook/kernel-locking.tmpl
parent8011b3c96f393b7ae95a6fd80e1634626c1b95ab (diff)
DocBook: fix various typos
This patch fixed spelling typo in various template files within Documentation/Docbook. Signed-off-by: Masanari Iida <standby24x7@gmail.com> Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/DocBook/kernel-locking.tmpl')
-rw-r--r--Documentation/DocBook/kernel-locking.tmpl2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/DocBook/kernel-locking.tmpl b/Documentation/DocBook/kernel-locking.tmpl
index 19f2a5a5a5b4..e584ee12a1e7 100644
--- a/Documentation/DocBook/kernel-locking.tmpl
+++ b/Documentation/DocBook/kernel-locking.tmpl
@@ -1760,7 +1760,7 @@ as it would be on UP.
</para>
<para>
-There is a furthur optimization possible here: remember our original
+There is a further optimization possible here: remember our original
cache code, where there were no reference counts and the caller simply
held the lock whenever using the object? This is still possible: if
you hold the lock, no one can delete the object, so you don't need to