From: Mark Brown <broonie@kernel.org>
To: Matthew Wilcox <willy@infradead.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: Wed, 26 Aug 2026 14:47:35 +0100 [thread overview]
Message-ID: <3d9f98a8-1df3-4b06-b1bf-42baba10d3a5@sirena.org.uk> (raw)
In-Reply-To: <ao3zvOo2nkMxaDY5@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On Tue, Aug 25, 2026 at 08:57:48PM +0100, Matthew Wilcox wrote:
> On Tue, Aug 25, 2026 at 02:44:54PM +0100, Mark Brown wrote:
> > 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.
> 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:
Looks like that did the trick for the build tests I do as part of -next
at least.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-08-26 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 17:00 Matthew Wilcox
2026-08-25 12:50 ` Mark Brown
2026-08-25 13:44 ` Mark Brown
2026-08-25 19:57 ` Matthew Wilcox
2026-08-26 13:47 ` Mark Brown [this message]
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=3d9f98a8-1df3-4b06-b1bf-42baba10d3a5@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®