linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
	Jeff Layton <jlayton@kernel.org>,
	linux-mm@kvack.org, linux-cachefs@redhat.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Request for folios
Date: Thu, 15 Jul 2021 20:39:01 +0100	[thread overview]
Message-ID: <YPCO1SuMyZ6j4Gno@casper.infradead.org> (raw)
In-Reply-To: <20210713191101.b38013786e36286e78c9648c@linux-foundation.org>

On Tue, Jul 13, 2021 at 07:11:01PM -0700, Andrew Morton wrote:
> > Also, is it possible to get the folios patchset in a stable public git branch
> > that I can base my patches upon?
> 
> I guess Willy's tree, but I doubt if the folio patches will be reliably
> stable for some time (a few weeks?)

So, how about I put the 89 patches which I want to merge this merge
window into a git branch which Dave can develop against?  Andrew can
pull that branch into mmotm when it's sufficiently settled for his taste.

In order for that to look good in Linus' tree, either Dave can send a
pull request which includes all of the folio patches, or I can send a
pull request early in the merge window (or even before the merge window
opens) which includes those 89 patches.

That would mean the patches wouldn't have Andrew's sign-off on them, but I
could add a R-b from Andrew to all of them if that's the right way to go.

      reply	other threads:[~2021-07-15 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12 15:43 Request for folios David Howells
2021-07-14  2:11 ` Andrew Morton
2021-07-15 19:39   ` Matthew Wilcox [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=YPCO1SuMyZ6j4Gno@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=jlayton@kernel.org \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).