From: lipeifeng@oppo.com
To: lipeifeng@oppo.com, hannes@cmpxchg.org, mhocko@kernel.org,
shakeel.butt@linux.dev, muchun.song@linux.dev
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] mm: fix the comment error of memcontrol.h
Date: Wed, 17 Apr 2024 20:16:45 +0800 [thread overview]
Message-ID: <20240417121645.25355-1-lipeifeng@oppo.com> (raw)
From: Peifeng Li <lipeifeng@oppo.com>
Signed-off-by: Peifeng Li <lipeifeng@oppo.com>
---
include/linux/memcontrol.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
index 394fd0a887ae..07d08be706bf 100644
--- a/include/linux/memcontrol.h
+++ b/include/linux/memcontrol.h
@@ -1679,7 +1679,7 @@ static inline bool folio_matches_lruvec(struct folio *folio,
lruvec_memcg(lruvec) == folio_memcg(folio);
}
-/* Don't lock again iff page's lruvec locked */
+/* Don't lock again if page's lruvec locked */
static inline struct lruvec *folio_lruvec_relock_irq(struct folio *folio,
struct lruvec *locked_lruvec)
{
@@ -1693,7 +1693,7 @@ static inline struct lruvec *folio_lruvec_relock_irq(struct folio *folio,
return folio_lruvec_lock_irq(folio);
}
-/* Don't lock again iff folio's lruvec locked */
+/* Don't lock again if folio's lruvec locked */
static inline void folio_lruvec_relock_irqsave(struct folio *folio,
struct lruvec **lruvecp, unsigned long *flags)
{
--
2.34.1
next reply other threads:[~2024-04-17 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 12:16 lipeifeng [this message]
2024-04-17 12:24 ` [PATCH] mm: fix the comment error of memcontrol.h Michal Hocko
2024-04-18 2:12 ` 李培锋
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=20240417121645.25355-1-lipeifeng@oppo.com \
--to=lipeifeng@oppo.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=shakeel.butt@linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).