From: Greg KH <gregkh@linuxfoundation.org>
To: Danilo Krummrich <dakr@kernel.org>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org, david@redhat.com,
mhocko@kernel.org, zhengqi.arch@bytedance.com,
shakeel.butt@linux.dev, lorenzo.stoakes@oracle.com,
rafael@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] mm/vmscan: fix inverted polarity in lru_gen_seq_show()
Date: Mon, 11 Aug 2025 07:27:06 +0200 [thread overview]
Message-ID: <2025081158-had-fracture-a5e6@gregkh> (raw)
In-Reply-To: <DBYXZ0RQ58Z7.2UBHDTZ2LCT2B@kernel.org>
On Sun, Aug 10, 2025 at 07:59:32PM +0200, Danilo Krummrich wrote:
> On Sun Jul 27, 2025 at 12:59 PM CEST, Danilo Krummrich wrote:
> > Commit a7694ff11aa9 ("vmscan: don't bother with debugfs_real_fops()")
> > started using debugfs_get_aux_num() to distinguish between the RW
> > "lru_gen" and the RO "lru_gen_full" file [1].
> >
> > Willy reported the inverted polarity [2] and Al fixed it up in [3].
> >
> > However, the patch in [1] was applied. Hence, fix this up accordingly.
> >
> > Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> > Cc: Matthew Wilcox <willy@infradead.org>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Link: https://lore.kernel.org/all/20250704040720.GP1880847@ZenIV/ [1]
> > Link: https://lore.kernel.org/all/aGZu3Z730FQtqxsE@casper.infradead.org/ [2]
> > Link: https://lore.kernel.org/all/20250704040720.GP1880847@ZenIV/ [3]
> > Fixes: a7694ff11aa9 ("vmscan: don't bother with debugfs_real_fops()")
> > Signed-off-by: Danilo Krummrich <dakr@kernel.org>
>
> Applied to driver-core-linus, thanks!
Sorry for the delay, thanks for queueing this up.
greg k-h
prev parent reply other threads:[~2025-08-11 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 10:59 [PATCH] mm/vmscan: fix inverted polarity in lru_gen_seq_show() Danilo Krummrich
2025-07-27 11:04 ` Greg KH
2025-08-10 17:59 ` Danilo Krummrich
2025-08-11 5:27 ` Greg KH [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=2025081158-had-fracture-a5e6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=dakr@kernel.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=rafael@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=zhengqi.arch@bytedance.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;
as well as URLs for NNTP newsgroup(s).