From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: David Hildenbrand <david@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: remove io-mapping
Date: Thu, 24 Jul 2025 17:19:41 +0100 [thread overview]
Message-ID: <4703a9a7-ad1f-493a-ac67-e6dea05cafb1@lucifer.local> (raw)
In-Reply-To: <ee6df343-6500-4443-9af1-4d15040e39c9@redhat.com>
On Thu, Jul 24, 2025 at 06:16:11PM +0200, David Hildenbrand wrote:
> On 24.07.25 17:39, Lorenzo Stoakes wrote:
> > Sorry Andrew please ignore this for now, I'll send a v2 later.
> >
> > I'm not having a great day here...
> >
> > I wrongly assumed that, since this is wholly unused in practice, that nobody
> > would refer to it or include the header, but it turns out that's incorrect.
>
> So, do we have to keep all (and keep it in MAINTAINERS) or is it just about
> cleaning up the headers?
No we don't have to keep, I just sent this patch, then Vlastimil pointed out
off-list that there were a bunch of includes that I missed.
It's matching about how my day is going.
I had wrongly assumed since there are no actual users, that nobody would just
import this header for no reason. But hey. They do.
Apparently docs also reference it.
I'll just send a v2 tomorrow.
Cheers, Lorenzo
next prev parent reply other threads:[~2025-07-24 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 14:53 Lorenzo Stoakes
2025-07-24 14:57 ` David Hildenbrand
2025-07-24 15:39 ` Lorenzo Stoakes
2025-07-24 16:16 ` David Hildenbrand
2025-07-24 16:19 ` Lorenzo Stoakes [this message]
2025-07-25 14:04 ` Lorenzo Stoakes
2025-07-24 18:53 ` Jonathan Corbet
2025-07-25 14:23 ` Lorenzo Stoakes
2025-07-26 10:15 ` kernel test robot
2025-07-26 17:39 ` Andrew Morton
2025-07-26 19:16 ` Lorenzo Stoakes
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=4703a9a7-ad1f-493a-ac67-e6dea05cafb1@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