summaryrefslogtreecommitdiffstats
path: root/libglusterfs/src/refcount.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 /libglusterfs/src/refcount.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 'libglusterfs/src/refcount.c')
-rw-r--r--libglusterfs/src/refcount.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/libglusterfs/src/refcount.c b/libglusterfs/src/refcount.c
index 5787da290bb..714bb9afef6 100644
--- a/libglusterfs/src/refcount.c
+++ b/libglusterfs/src/refcount.c
@@ -21,7 +21,7 @@ _gf_ref_get (gf_ref_t *ref)
/* if cnt == 0, we're in a fatal position, the object will be free'd
*
* There is a race when two threads do a _gf_ref_get(). Only one of
- * them may get a 0 returned. That is acceptible, because one
+ * them may get a 0 returned. That is acceptable, because one
* _gf_ref_get() returning 0 should be handled as a fatal problem and
* when correct usage/locking is used, it should never happen.
*/