From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org, weijie.yang@samsung.com,
vitaly.wool@konsulko.com, sjennings@variantweb.net,
sjenning@redhat.com, ddstreet@ieee.org, rdunlap@infradead.org
Subject: + mm-zswap-clean-up-confusing-comment.patch added to -mm tree
Date: Tue, 22 Dec 2020 17:01:32 -0800 [thread overview]
Message-ID: <20201223010132.pew1O%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm: zswap: clean up confusing comment
has been added to the -mm tree. Its filename is
mm-zswap-clean-up-confusing-comment.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/mm-zswap-clean-up-confusing-comment.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/mm-zswap-clean-up-confusing-comment.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Randy Dunlap <rdunlap@infradead.org>
Subject: mm: zswap: clean up confusing comment
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>
---
mm/zswap.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- a/mm/zswap.c~mm-zswap-clean-up-confusing-comment
+++ a/mm/zswap.c
@@ -1022,10 +1022,10 @@ static int zswap_writeback_entry(struct
/*
* 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);
_
Patches currently in -mm which might be from rdunlap@infradead.org are
zlib-move-export_symbol-and-module_license-out-of-dfltcc_symsc.patch
mm-zswap-clean-up-confusing-comment.patch
reply other threads:[~2020-12-23 1:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201223010132.pew1O%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sjenning@redhat.com \
--cc=sjennings@variantweb.net \
--cc=vitaly.wool@konsulko.com \
--cc=weijie.yang@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox