From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Andreas Gruenbacher <agruenba@redhat.com>
Subject: Re: [ANNOUNCE] xfs-linux: iomap-5.4-merge rebased to 1b4fdf4f30db
Date: Thu, 19 Sep 2019 21:28:16 +0000 [thread overview]
Message-ID: <BYAPR04MB58169EE2BC3346CF6CC3C61BE7890@BYAPR04MB5816.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20190919170804.GB1646@infradead.org
On 2019/09/19 19:08, Christoph Hellwig wrote:
> On Thu, Sep 19, 2019 at 04:19:37PM +0000, Damien Le Moal wrote:
>> OK. Will do, but traveling this week so I will not be able to test until next week.
>
> Which suggests zonefs won't make it for 5.4, right? At that point
Yes, Linus did not accept zonefs for 5.4. He requested that I first get more
comments about it, adding lkml in the loop to increase the reach over the more
limited attendance of linux-xfs and linux-fsdevel lists. The other request is to
repost early in the 5.4 cycle and get zonefs into linux-next to go through more
build tests too.
> I wonder if we should defer the whole generic iomap writeback thing
> to 5.5 entirely. The whole idea of having two copies of the code always
> scared me, even more so given that 5.4 is slated to be a long term
> stable release.
>
> So maybe just do the trivial typo + end_io cleanups for Linus this
> merge window?
>
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2019-09-19 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 15:37 [ANNOUNCE] xfs-linux: iomap-5.4-merge rebased to 1b4fdf4f30db Darrick J. Wong
2019-09-19 16:19 ` Damien Le Moal
2019-09-19 17:08 ` Christoph Hellwig
2019-09-19 19:40 ` Darrick J. Wong
2019-09-19 21:03 ` Christoph Hellwig
2019-09-19 21:19 ` Damien Le Moal
2019-09-19 21:28 ` Damien Le Moal [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=BYAPR04MB58169EE2BC3346CF6CC3C61BE7890@BYAPR04MB5816.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=agruenba@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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.