mm: zswap: clean up confusing comment
authorRandy Dunlap <rdunlap@infradead.org>
Fri, 26 Feb 2021 01:18:13 +0000 (17:18 -0800)
committerLinus Torvalds <torvalds@linux-foundation.org>
Fri, 26 Feb 2021 17:41:01 +0000 (09:41 -0800)
Correct wording and change one duplicated word (it) to "it is".

Link: https://lkml.kernel.org/r/20201221042848.13980-1-rdunlap@infradead.org
Fixes: 0ab0abcf5115 ("mm/zswap: refactor the get/put routines")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Weijie Yang <weijie.yang@samsung.com>
Cc: Seth Jennings <sjennings@variantweb.net>
Cc: Seth Jennings <sjenning@redhat.com>
Cc: Dan Streetman <ddstreet@ieee.org>
Cc: Vitaly Wool <vitaly.wool@konsulko.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
mm/zswap.c

index 182f6ad..1e41c28 100644 (file)
@@ -1022,10 +1022,10 @@ static int zswap_writeback_entry(struct zpool *pool, unsigned long handle)
 
        /*
        * if we get here due to ZSWAP_SWAPCACHE_EXIST
-       * a load may happening concurrently
-       * it is safe and okay to not free the entry
+       * a load may be happening concurrently.
+       * it is safe and okay to not free the entry.
        * if we free the entry in the following put
-       * it it either okay to return !0
+       * it is also okay to return !0
        */
 fail:
        spin_lock(&tree->lock);