The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Mark Brown <broonie@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Please include pagemap header cleanup in -next
Date: Mon, 24 Aug 2026 18:00:47 +0100	[thread overview]
Message-ID: <aox4v6paR4IbJr8j@casper.infradead.org> (raw)

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.

             reply	other threads:[~2026-08-24 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 17:00 Matthew Wilcox [this message]
2026-08-25 12:50 ` Please include pagemap header cleanup in -next Mark Brown
2026-08-25 13:44 ` Mark Brown
2026-08-25 19:57   ` Matthew Wilcox

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=aox4v6paR4IbJr8j@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@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