From: Andrew Morton <akpm@linux-foundation.org>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: David Hildenbrand <david@redhat.com>,
Qingshuang Fu <fffsqian@163.com>,
hannes@cmpxchg.org, mhocko@kernel.org,
zhengqi.arch@bytedance.com, lorenzo.stoakes@oracle.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Qingshuang Fu <fuqingshuang@kylinos.cn>,
Yuanchu Xie <yuanchu@google.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [PATCH] Fix the data type inconsistency issue of min (tier, MAX_CR_TIERS-1) in read_ctrl_pos
Date: Wed, 13 Aug 2025 14:41:45 -0700 [thread overview]
Message-ID: <20250813144145.cf6eece4d1d746568c39bd86@linux-foundation.org> (raw)
In-Reply-To: <CAJHvVchDq-p77VbzO53nNxMTZ-5okMp1SUSQfw_VD3f75fFgAQ@mail.gmail.com>
On Wed, 13 Aug 2025 13:03:42 -0700 Axel Rasmussen <axelrasmussen@google.com> wrote:
> >
> >
> > (cc mglru maintainers, who have yet to reveal themselves in MAINTAINERS)
>
> Sorry for that, I took a look at adding myself and Yuanchu, but it
> wasn't clear how to represent MGLRU in MAINTAINERS, because there
> isn't a mglru.c, it's bolted on to several existing files with
> existing maintainers. Should us two just be appended to the list of
> folks for vmscan.c, or?
I think a separate MGLRU section which mentions mm/vmscan.c is
appropriate. kernel/fork.c gets a mention in three sections.
next prev parent reply other threads:[~2025-08-13 21:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 7:21 [PATCH] Fix the data type inconsistency issue of min (tier, MAX_CR_TIERS-1) in read_ctrl_pos Qingshuang Fu
2025-08-08 7:35 ` David Hildenbrand
2025-08-08 9:26 ` fffsqian
2025-08-08 9:32 ` David Hildenbrand
2025-08-12 4:40 ` Andrew Morton
2025-08-13 20:03 ` Axel Rasmussen
2025-08-13 21:41 ` Andrew Morton [this message]
2025-08-14 5:40 ` Lorenzo Stoakes
2025-08-14 11:51 ` David Laight
2025-08-14 21:26 ` David Laight
-- strict thread matches above, loose matches on Subject: below --
2025-08-08 7:34 Qingshuang Fu
2025-08-08 9:27 Qingshuang Fu
2025-08-08 9:42 ` David Hildenbrand
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=20250813144145.cf6eece4d1d746568c39bd86@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=david@redhat.com \
--cc=fffsqian@163.com \
--cc=fuqingshuang@kylinos.cn \
--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=yuanchu@google.com \
--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).