From: Matthew Wilcox <willy@infradead.org>
To: Mark Brown <broonie@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Please include pagemap header cleanup in -next
Date: Tue, 25 Aug 2026 20:57:48 +0100 [thread overview]
Message-ID: <ao3zvOo2nkMxaDY5@casper.infradead.org> (raw)
In-Reply-To: <29f8f296-e49c-4960-aadb-f27d863ba773@sirena.org.uk>
On Tue, Aug 25, 2026 at 02:44:54PM +0100, Mark Brown wrote:
> On Mon, Aug 24, 2026 at 06:00:47PM +0100, Matthew Wilcox wrote:
> > Hi Mark,
> >
> > As discussed on IRC, please include
> >
> > git://git.infradead.org/users/willy/pagecache.git headers
> >
> > The net effect is to reduce the number of files depending on pagemap.h
> > from ~9100 to ~1400 on an x86 allmodconfig build. The Intel test robot
> > has been steadily building random configs on random architectures and
> > finding new missing includes, so there may be some build breakages that
> > it hasn't tested.
> >
> > My plan is to send this to Linus on Thursday or Friday. I don't see the
> > point in letting it soak longer; any problems it causes are build
> > problems.
>
> As I noted in the regular build error mail it hit a build fail on an arm
> multi_v7_defconfig so I didn't merge this today. It's pretty surprising
> that the build bot didn't hit that one TBH since the file that broke
> hasn't changed since v7.2 AFAICT, I would guess that there's some other
> implicit include cleanup work that's interacting badly with this effort
> but I haven't investigated at all.
>
> BTW I added the -next list, please CC requests for -next there for
> visibility.
Thanks; I looked for it in the Documentation and didn't find it.
I fixed up the one you mentioned Then I installed an arm32
crosscompiler and built arm allmodconfig. And then Intel's test robot
found another. So in total, three more fixes:
drivers/dma/ste_dma40.c
drivers/ufs/host/ufs-qcom.c
drivers/gpu/drm/amd/amdkfd/kfd_migrate.c
Pushed out a new version (e02cb91d4644)
next prev parent reply other threads:[~2026-08-25 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aox4v6paR4IbJr8j@casper.infradead.org>
2026-08-25 13:44 ` Please include pagemap header cleanup in -next Mark Brown
2026-08-25 19:57 ` Matthew Wilcox [this message]
2026-08-26 13:47 ` Mark Brown
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=ao3zvOo2nkMxaDY5@casper.infradead.org \
--to=willy@infradead.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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