From: Andreas Gruenbacher <agruenba@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Gao Xiang <hsiangkao@linux.alibaba.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 00:31:39 +0200 [thread overview]
Message-ID: <CAHc6FU5YAs-8HZAVeP-ZWRmvZ3mXDs37SgWXXOJC+uS=6hTVgw@mail.gmail.com> (raw)
In-Reply-To: <20210802221114.GG3601466@magnolia>
On Tue, Aug 3, 2021 at 12:11 AM Darrick J. Wong <djwong@kernel.org> 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.
>
> 3. Matthew also threw in a patch:
>
> iomap: Support inline data with block size < page size
>
> for which Andreas also sent some suggestions, so I guess I'm waiting for
> a v2 of that patch? It looks to me like the last time he sent that
> series (on 24 July) he incorporated Gao's patch as patch 1 of the
> series?
>
> 4. Andreas has a patch:
>
> iomap: Fix some typos and bad grammar
>
> which looks more or less ready to go.
>
> 5. Christoph also had a series:
>
> RFC: switch iomap to an iterator model
>
> Which I reviewed and sent some comments for, but (AFAICT) haven't seen a
> non-RFC resubmission yet. Is that still coming for 5.15?
>
> 6. Earlier, Eric Biggers had a patchset that made some iomap changes
> ahead of porting f2fs to use directio. I /think/ those changes were
> dropped in the latest submission because the intended use of those
> changes (counters of the number of pages undergoing reads or writes,
> iirc?) has been replaced with something simpler. IOWs, f2fs doesn't
> need any iomap changes for 5.15, right?
>
> 7. Andreas also had a patchset:
>
> gfs2: Fix mmap + page fault deadlocks
>
> That I've left unread because Linus started complaining about patch 1.
> Is that not going forward, then?
Still working on it; it's way nastier than expected.
> So, I /think/ that's all I've received for this next cycle. Did I miss
> anything? Matthew said he might roll some of these up and send me a
> pull request, which would be nice... :)
>
> --D
>
Andreas
next prev parent reply other threads:[~2021-08-02 22:31 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 [this message]
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
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='CAHc6FU5YAs-8HZAVeP-ZWRmvZ3mXDs37SgWXXOJC+uS=6hTVgw@mail.gmail.com' \
--to=agruenba@redhat.com \
--cc=djwong@kernel.org \
--cc=ebiggers@kernel.org \
--cc=hch@infradead.org \
--cc=hsiangkao@linux.alibaba.com \
--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).