From: SeongJae Park <sj@kernel.org>
To: Greg Thelen <gthelen@google.com>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Shakeel Butt <shakeel.butt@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memcg-v1: remove folio_memcg_lock() doc reference
Date: Fri, 2 Jan 2026 15:56:43 -0800 [thread overview]
Message-ID: <20260102235644.54611-1-sj@kernel.org> (raw)
In-Reply-To: <20260101225552.3423108-1-gthelen@google.com>
On Thu, 1 Jan 2026 14:55:51 -0800 Greg Thelen <gthelen@google.com> wrote:
> Commit a29c0e4b2e86 ("memcg-v1: remove memcg move locking code") removed
> folio_memcg_lock(). Delete the final lingering documentation reference.
Nice cleanup!
>
> Fixes: a29c0e4b2e86 ("memcg-v1: remove memcg move locking code")
> Signed-off-by: Greg Thelen <gthelen@google.com>
Acked-by: SeongJae Park <sj@kernel.org>
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-01-02 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 22:55 Greg Thelen
2026-01-02 2:43 ` Shakeel Butt
2026-01-02 23:56 ` SeongJae Park [this message]
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=20260102235644.54611-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gthelen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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