From: "Darrick J. Wong" <djwong@kernel.org>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Gao Xiang <hsiangkao@linux.alibaba.com>,
Andreas Gruenbacher <agruenba@redhat.com>,
Eric Biggers <ebiggers@kernel.org>
Subject: [ANNOUNCE] xfs-linux: iomap-5.15-merge updated to ae44f9c286da
Date: Thu, 5 Aug 2021 11:22:40 -0700 [thread overview]
Message-ID: <20210805182240.GX3601443@magnolia> (raw)
Hi folks,
The iomap-5.15-merge branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
Patches often get missed, so please check if your outstanding patches
were in this update. If they have not been in this update, please
resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
the next update. Just sneaking in a couple more patches from Matthew
Wilcox so that (presumably) Christoph has a stable place to rebase the
iomap_iter series.
The new head of the iomap-5.15-merge branch is commit:
ae44f9c286da iomap: Add another assertion to inline data handling
New Commits:
Andreas Gruenbacher (1):
[f1f264b4c134] iomap: Fix some typos and bad grammar
Christoph Hellwig (2):
[d0364f9490d7] iomap: simplify iomap_readpage_actor
[c1b79f11f4ec] iomap: simplify iomap_add_to_ioend
Gao Xiang (1):
[69f4a26c1e0c] iomap: support reading inline data from non-zero pos
Matthew Wilcox (Oracle) (3):
[b405435b419c] iomap: Support inline data with block size < page size
[ab069d5fdcd1] iomap: Use kmap_local_page instead of kmap_atomic
[ae44f9c286da] iomap: Add another assertion to inline data handling
Code Diffstat:
fs/iomap/buffered-io.c | 165 +++++++++++++++++++++++++------------------------
fs/iomap/direct-io.c | 10 +--
include/linux/iomap.h | 18 ++++++
3 files changed, 108 insertions(+), 85 deletions(-)
reply other threads:[~2021-08-05 18:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210805182240.GX3601443@magnolia \
--to=djwong@kernel.org \
--cc=agruenba@redhat.com \
--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).