From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: David Hildenbrand <david@redhat.com>,
Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] MAINTAINERS: add further core files to mm core section
Date: Tue, 22 Jul 2025 14:53:38 +0100 [thread overview]
Message-ID: <33c605a6-2b89-4b40-ba80-ed2ca665ef5a@lucifer.local> (raw)
In-Reply-To: <aFDm0YrbSAvXc5Wp@kernel.org>
On Tue, Jun 17, 2025 at 06:53:53AM +0300, Mike Rapoport wrote:
>
> > > +F: mm/io-mapping.c
>
> This is an interesting one. There are no in tree users of the only function
> it contains.
Hi Christoph,
Was going through and making sure mm files have places in MAINTAINERS and
came across this - I see you added this, but it doesn't appear to be being
used anywhere. Should it be removed or if not wonder where it ought to go?
We're contemplating an 'MM MISC' section where it could live potentially.
Cheers, Lorenzo
next prev parent reply other threads:[~2025-07-22 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 20:38 Lorenzo Stoakes
2025-06-16 21:10 ` David Hildenbrand
2025-06-16 22:56 ` Shakeel Butt
2025-06-17 15:22 ` Lorenzo Stoakes
2025-06-17 17:51 ` Shakeel Butt
2025-06-17 17:55 ` Lorenzo Stoakes
2025-06-17 3:53 ` Mike Rapoport
2025-06-17 7:59 ` David Hildenbrand
2025-06-17 15:04 ` Lorenzo Stoakes
2025-06-17 15:46 ` David Hildenbrand
2025-07-22 13:53 ` Lorenzo Stoakes [this message]
2025-07-22 14:22 ` Vlastimil Babka
2025-07-23 5:36 ` Christoph Hellwig
2025-06-17 15:26 ` Lorenzo Stoakes
2025-06-19 5:31 ` Alistair Popple
2025-06-17 18:47 ` Vlastimil Babka
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=33c605a6-2b89-4b40-ba80-ed2ca665ef5a@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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