mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [GIT PULL] Remove dependencies on pagemap.h
Date: Fri, 28 Aug 2026 18:33:41 +0100	[thread overview]
Message-ID: <apHGdfwY67YZ4sEr@casper.infradead.org> (raw)
In-Reply-To: <CAHk-=wimz+APb9hGEry+vHDLB5D7WZvNGWU89HjGw7wH15KGHg@mail.gmail.com>

On Fri, Aug 28, 2026 at 10:26:22AM -0700, Linus Torvalds wrote:
> On Fri, 28 Aug 2026 at 10:18, Matthew Wilcox <willy@infradead.org> wrote:
> >
> > OK.  I thought you liked this kind of churn stuff at the end of the window,
> > rather than having it create random unnecesary conflicts throughout the
> > development cycle.  Have you changed your mind on that?
> 
> I like things like automated churn at the end - IF I HAVE BEEN TOLD
> ABOUT AHEAD OF TIME and know to expect it, and people have said "this
> is scripted stuff that can cause conflicts, so I'd suggest we do it
> just after rc1 when all the big stuff is merged".
> 
> But I absolutely do *NOT* want to see a random pull that is broken in
> other ways popping up on the Friday before the merge window closes
> that has never been in linux-next and has never been explicitly talked
> about with me beforehand.

How far in advance do you want to know about it?  Because I did send you
email about it a few days ago; must've got lost.  It has been in
linux-next for a few days (would have been longer, but the Intel test
robot kept finding random drivers and configs that had build problems).
It's already generating conflicts with other header file changes, and
that's just going to be amplified throughout a whole development cycle.

I'd love to script this, but I just don't think that's possible.

  reply	other threads:[~2026-08-28 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 16:51 Matthew Wilcox
2026-08-28 16:56 ` Linus Torvalds
2026-08-28 17:18   ` Matthew Wilcox
2026-08-28 17:26     ` Linus Torvalds
2026-08-28 17:33       ` Matthew Wilcox [this message]
2026-08-28 17:42         ` Linus Torvalds

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=apHGdfwY67YZ4sEr@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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

all inboxes | Powered by JetHome®