Re: [PATCH] memcg-v1: remove folio_memcg_lock() doc reference

From: SeongJae Park
Date: Fri Jan 02 2026 - 18:56:57 EST

Next message: Alexei Starovoitov: "Re: [PATCH bpf-next 0/4] bpf: tailcall: Eliminate max_entries and bpf_func access at runtime"
Previous message: Jakub Kicinski: "Re: [PATCH v1 10/23] net: ethernet: ti: am65-cpsw: Discard pm_runtime_put() return value"
In reply to: Shakeel Butt: "Re: [PATCH] memcg-v1: remove folio_memcg_lock() doc reference"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, 1 Jan 2026 14:55:51 -0800 Greg Thelen <gthelen@xxxxxxxxxx> 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@xxxxxxxxxx>

Acked-by: SeongJae Park <sj@xxxxxxxxxx>

Thanks,
SJ

[...]

Next message: Alexei Starovoitov: "Re: [PATCH bpf-next 0/4] bpf: tailcall: Eliminate max_entries and bpf_func access at runtime"
Previous message: Jakub Kicinski: "Re: [PATCH v1 10/23] net: ethernet: ti: am65-cpsw: Discard pm_runtime_put() return value"
In reply to: Shakeel Butt: "Re: [PATCH] memcg-v1: remove folio_memcg_lock() doc reference"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]