summaryrefslogtreecommitdiff
path: root/include/linux/brlock.h
diff options
context:
space:
mode:
authorJames Mayer <james@cobaltmountain.com>2002-07-14 22:56:42 -0700
committerLinus Torvalds <torvalds@penguin.transmeta.com>2002-07-14 22:56:42 -0700
commit82103c8396f5c701d7fb1f470becffacb9254d85 (patch)
treec0da5f9c7742206e6fe4028a06316ff2f2322d83 /include/linux/brlock.h
parent70d6d4bf1622b31e6b43e06eb5745cc51cc77de9 (diff)
[PATCH] Typo in linux_include_linux_brlock.h
Diffstat (limited to 'include/linux/brlock.h')
-rw-r--r--include/linux/brlock.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/brlock.h b/include/linux/brlock.h
index 68c200512604..81d87c72ca1d 100644
--- a/include/linux/brlock.h
+++ b/include/linux/brlock.h
@@ -19,7 +19,7 @@
*
* David S. Miller <davem@redhat.com>
*
- * David has an implementation that doesnt use atomic operations in
+ * David has an implementation that doesn't use atomic operations in
* the read branch via memory ordering tricks - i guess we need to
* split this up into a per-arch thing? The atomicity issue is a
* secondary item in profiles, at least on x86 platforms.