[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250813144145.cf6eece4d1d746568c39bd86@linux-foundation.org>
Date: Wed, 13 Aug 2025 14:41:45 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Axel Rasmussen <axelrasmussen@...gle.com>
Cc: David Hildenbrand <david@...hat.com>, Qingshuang Fu <fffsqian@....com>,
hannes@...xchg.org, mhocko@...nel.org, zhengqi.arch@...edance.com,
lorenzo.stoakes@...cle.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Qingshuang Fu <fuqingshuang@...inos.cn>,
Yuanchu Xie <yuanchu@...gle.com>, Lorenzo Stoakes
<lorenzo.stoakes@...cle.com>
Subject: Re: [PATCH] Fix the data type inconsistency issue of min (tier,
MAX_CR_TIERS-1) in read_ctrl_pos
On Wed, 13 Aug 2025 13:03:42 -0700 Axel Rasmussen <axelrasmussen@...gle.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.
Powered by blists - more mailing lists