aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/staging/lustre/lustre/include/lustre_dlm_flags.h
diff options
context:
space:
mode:
authorMasanari Iida <standby24x7@gmail.com>2014-03-08 22:58:33 +0900
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-03-08 19:33:11 -0800
commit17891183d08038655d60c1f3c894a8502cd5d7c1 (patch)
tree3b4419181a0ad4733e5fa1a120fc9475239eecd2 /drivers/staging/lustre/lustre/include/lustre_dlm_flags.h
parentstaging: luster: Fix typo in lustre/llite (diff)
downloadlinux-dev-17891183d08038655d60c1f3c894a8502cd5d7c1.tar.xz
linux-dev-17891183d08038655d60c1f3c894a8502cd5d7c1.zip
staging: lustre: Fix typo in lustre/include part1
Fix typo in comments within lustre/include. Signed-off-by: Masanari Iida <standby24x7@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/lustre/lustre/include/lustre_dlm_flags.h')
-rw-r--r--drivers/staging/lustre/lustre/include/lustre_dlm_flags.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/staging/lustre/lustre/include/lustre_dlm_flags.h b/drivers/staging/lustre/lustre/include/lustre_dlm_flags.h
index 73fb38ee0a34..16dcdbfae689 100644
--- a/drivers/staging/lustre/lustre/include/lustre_dlm_flags.h
+++ b/drivers/staging/lustre/lustre/include/lustre_dlm_flags.h
@@ -147,7 +147,7 @@
#define ldlm_clear_test_lock(_l) LDLM_CLEAR_FLAG((_l), 1ULL << 19)
/**
- * Immediatelly cancel such locks when they block some other locks. Send
+ * Immediately cancel such locks when they block some other locks. Send
* cancel notification to original lock holder, but expect no reply. This
* is for clients (like liblustre) that cannot be expected to reliably
* response to blocking AST. */
@@ -248,7 +248,7 @@
/**
* A lock contributes to the known minimum size (KMS) calculation until it
- * has finished the part of its cancelation that performs write back on its
+ * has finished the part of its cancellation that performs write back on its
* dirty pages. It can remain on the granted list during this whole time.
* Threads racing to update the KMS after performing their writeback need
* to know to exclude each other's locks from the calculation as they walk