summaryrefslogtreecommitdiffstats
path: root/xlators/performance/nl-cache/src/nl-cache-helper.c
diff options
context:
space:
mode:
authorYaniv Kaul <ykaul@redhat.com>2018-07-16 17:03:17 +0300
committerAmar Tumballi <amarts@redhat.com>2018-07-22 14:40:16 +0000
commit621138ce763eda8270d0a4f6d7209fd50ada8787 (patch)
tree7299759993f6e9f7f34dad95fc8d8cd6ffc1b2fd /xlators/performance/nl-cache/src/nl-cache-helper.c
parentc0e76377d0fc47aa66f35ea70a4793731ebbd40c (diff)
All: run codespell on the code and fix issues.
Please review, it's not always just the comments that were fixed. I've had to revert of course all calls to creat() that were changed to create() ... Only compile-tested! Change-Id: I7d02e82d9766e272a7fd9cc68e51901d69e5aab5 updates: bz#1193929 Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
Diffstat (limited to 'xlators/performance/nl-cache/src/nl-cache-helper.c')
-rw-r--r--xlators/performance/nl-cache/src/nl-cache-helper.c8
1 files changed, 4 insertions, 4 deletions
diff --git a/xlators/performance/nl-cache/src/nl-cache-helper.c b/xlators/performance/nl-cache/src/nl-cache-helper.c
index 67b17af8b69..b6b60a74918 100644
--- a/xlators/performance/nl-cache/src/nl-cache-helper.c
+++ b/xlators/performance/nl-cache/src/nl-cache-helper.c
@@ -23,14 +23,14 @@
* are sent before creating the file. Hence the negative entry cache.
* It can exist even when the positive entry cache is invalid. It also
* has the entries that were deleted from this directory.
- * Freed on recieving upcall(with dentry change flag) or on expiring
+ * Freed on receiving upcall(with dentry change flag) or on expiring
* timeout of the cache.
*
* - Positive entries: Populated as a part of readdirp, and as a part of
* mkdir followed by creates inside that directory. Lookups and other
* fops do not populate the positive entry (as it can grow long and is
* of no value add)
- * Freed on recieving upcall(with dentry change flag) or on expiring
+ * Freed on receiving upcall(with dentry change flag) or on expiring
* timeout of the cache.
*
* Data structures to store cache?
@@ -172,7 +172,7 @@ nlc_inode_ctx_set (xlator_t *this, inode_t *inode, nlc_ctx_t *nlc_ctx,
int ret = -1;
/* The caller may choose to set one of the ctxs, hence check
- * if the ctx1/2 is non zero and then send the adress. If we
+ * if the ctx1/2 is non zero and then send the address. If we
* blindly send the address of both the ctxs, it may reset the
* ctx the caller had sent NULL(intended as leave untouched) for.*/
LOCK(&inode->lock);
@@ -903,7 +903,7 @@ nlc_dir_add_ne (xlator_t *this, inode_t *inode, const char *name)
LOCK (&nlc_ctx->lock);
{
- /* There is one possiblility where we need to search before
+ /* There is one possibility where we need to search before
* adding NE: when there are two parallel lookups on a non
* existent file */
if (!__nlc_search_ne (nlc_ctx, name)) {