From: Vlastimil Babka <vbabka@suse.cz>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
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>,
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 16:22:59 +0200 [thread overview]
Message-ID: <bdca2e2e-acdb-4ea5-9017-6c1a58353452@suse.cz> (raw)
In-Reply-To: <33c605a6-2b89-4b40-ba80-ed2ca665ef5a@lucifer.local>
On 7/22/25 15:53, Lorenzo Stoakes wrote:
> 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?
It seems it only gained its only user in b739f125e4eb ("i915: use
io_mapping_map_user") but reverted a month later by 0e4fe0c9f2f9 ("Revert
"i915: use io_mapping_map_user"") all that in 2021.
Ideally i915 would be converted again with the revert reasons investigated
properly this time. Otherwise we should remove the thing.
> We're contemplating an 'MM MISC' section where it could live potentially.
>
> Cheers, Lorenzo
next prev parent reply other threads:[~2025-07-22 14:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 20:38 [RFC PATCH] MAINTAINERS: add further core files to mm core section 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
2025-07-22 14:22 ` Vlastimil Babka [this message]
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=bdca2e2e-acdb-4ea5-9017-6c1a58353452@suse.cz \
--to=vbabka@suse.cz \
--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=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.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).