From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Folio tree for next
Date: Tue, 20 Jul 2021 19:29:27 -0700 [thread overview]
Message-ID: <20210720192927.98ee7809717b9cc28fa95bb6@linux-foundation.org> (raw)
In-Reply-To: <20210721122102.38c80140@canb.auug.org.au>
On Wed, 21 Jul 2021 12:21:02 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Matthew,
>
> On Tue, 20 Jul 2021 03:55:44 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> >
> > I think conceptually, the folio for-next tree is part of mmotm for this
> > cycle. I would have asked Andrew to carry these patches, but there are
> > people (eg Dave Howells) who want to develop against them. And that's
> > hard to do with patches that are in mmotm.
> >
> > So if Andrew bases mmotm on the folio tree for this cycle, does that
> > make sense?
>
> Sure. I will have a little pain the first day it appears, but it
> should be OK after that. I am on leave starting Saturday, so if you
> could get me a tree without the mmotm patches for tomorrow that would
> be good.
Sure, let's go that way. Linus wasn't terribly enthusiastic about the
folio patches and I can't claim to be overwhelmed by their value/churn
ratio (but many MM developers are OK with it all, and that
counts). Doing it this way retains options...
next prev parent reply other threads:[~2021-07-21 2:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 3:18 Folio tree for next Matthew Wilcox
2021-07-19 3:57 ` Andrew Morton
2021-07-19 23:40 ` Stephen Rothwell
2021-07-19 23:51 ` Stephen Rothwell
2021-07-20 2:55 ` Matthew Wilcox
2021-07-21 2:21 ` Stephen Rothwell
2021-07-21 2:29 ` Andrew Morton [this message]
2021-07-21 2:46 ` Matthew Wilcox
2021-07-21 3:22 ` Andrew Morton
2021-07-21 3:22 ` Matthew Wilcox
2021-07-21 5:04 ` Stephen Rothwell
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=20210720192927.98ee7809717b9cc28fa95bb6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sfr@canb.auug.org.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.