From: "Darrick J. Wong" <djwong@kernel.org>
To: Matthew Wilcox <willy@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Andreas Gruenbacher <agruenba@redhat.com>,
Eric Biggers <ebiggers@kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: iomap 5.15 branch construction ...
Date: Tue, 3 Aug 2021 09:42:51 -0700 [thread overview]
Message-ID: <20210803164251.GD3601405@magnolia> (raw)
In-Reply-To: <YQiMFsO5DQouSPs/@B-P7TQMD6M-0146.local>
On Tue, Aug 03, 2021 at 08:21:42AM +0800, Gao Xiang wrote:
> On Mon, Aug 02, 2021 at 03:11:14PM -0700, Darrick J. Wong wrote:
> > Hi everyone!
> >
> > iomap has become very popular for this cycle, with seemingly a lot of
> > overlapping patches and whatnot. Does this accurately reflect all the
> > stuff that people are trying to send for 5.15?
> >
> > 1. So far, I think these v2 patches from Christoph are ready to go:
> >
> > iomap: simplify iomap_readpage_actor
> > iomap: simplify iomap_add_to_ioend
> >
> > 2. This is the v9 "iomap: Support file tail packing" patch from Gao,
> > with a rather heavily edited commit:
> >
> > iomap: support reading inline data from non-zero pos
> >
> > Should I wait for a v10 patch with spelling fixes as requested by
> > Andreas? And if there is a v10 submission, please update the commit
> > message.
>
> I've already sent out v10 with these changes:
> https://lore.kernel.org/r/20210803001727.50281-1-hsiangkao@linux.alibaba.com
Applied, thanks.
--D
>
> Thanks,
> Gao Xiang
next prev parent reply other threads:[~2021-08-03 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 22:11 iomap 5.15 branch construction Darrick J. Wong
2021-08-02 22:31 ` Andreas Gruenbacher
2021-08-02 22:34 ` Eric Biggers
2021-08-03 16:42 ` Darrick J. Wong
2021-08-03 0:21 ` Gao Xiang
2021-08-03 16:42 ` Darrick J. Wong [this message]
2021-08-03 3:21 ` Matthew Wilcox
2021-08-03 8:17 ` Christoph Hellwig
2021-08-03 8:40 ` Dave Chinner
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=20210803164251.GD3601405@magnolia \
--to=djwong@kernel.org \
--cc=agruenba@redhat.com \
--cc=ebiggers@kernel.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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 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).