From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, libang.linuxer@gmail.com,
akpm@linux-foundation.org
Subject: + mm-swap-fix-confusing-comment-in-folio_mark_accessed.patch added to -mm tree
Date: Fri, 11 Mar 2022 14:14:06 -0800 [thread overview]
Message-ID: <20220311221407.8FBA1C340E9@smtp.kernel.org> (raw)
The patch titled
Subject: mm/swap: fix confusing comment in folio_mark_accessed
has been added to the -mm tree. Its filename is
mm-swap-fix-confusing-comment-in-folio_mark_accessed.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/mm-swap-fix-confusing-comment-in-folio_mark_accessed.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/mm-swap-fix-confusing-comment-in-folio_mark_accessed.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: Bang Li <libang.linuxer@gmail.com>
Subject: mm/swap: fix confusing comment in folio_mark_accessed
For unevictable pages, we don't need mark them.
Link: https://lkml.kernel.org/r/20220311141519.59948-1-libang.linuxer@gmail.com
Signed-off-by: Bang Li <libang.linuxer@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/swap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/swap.c~mm-swap-fix-confusing-comment-in-folio_mark_accessed
+++ a/mm/swap.c
@@ -425,7 +425,7 @@ void folio_mark_accessed(struct folio *f
/*
* Unevictable pages are on the "LRU_UNEVICTABLE" list. But,
* this list is never rotated or maintained, so marking an
- * evictable page accessed has no effect.
+ * unevictable page accessed has no effect.
*/
} else if (!folio_test_active(folio)) {
/*
_
Patches currently in -mm which might be from libang.linuxer@gmail.com are
mm-swap-fix-confusing-comment-in-folio_mark_accessed.patch
mm-vmalloc-fix-comments-about-vmap_area-struct.patch
reply other threads:[~2022-03-11 22:46 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=20220311221407.8FBA1C340E9@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=libang.linuxer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.