From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: iomap-for-next updated to d74999c8c060
Date: Wed, 11 May 2022 09:56:53 -0700 [thread overview]
Message-ID: <20220511165653.GG27195@magnolia> (raw)
Hi folks,
The iomap-for-next branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
Now that 5.18 has finally stabilized enough for fstests to pass again,
I'm finally ready to push the 5.19 iomap stuff.
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. The iomap changes for supporting biosets for directio
will be landing through the btrfs tree, which leaves only these two bug
fixes that Andreas sent earlier.
The new head of the iomap-for-next branch is commit:
d74999c8c060 iomap: iomap_write_end cleanup
2 new commits:
Andreas Gruenbacher (2):
[b71450e2cc4b] iomap: iomap_write_failed fix
[d74999c8c060] iomap: iomap_write_end cleanup
Code Diffstat:
fs/iomap/buffered-io.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
reply other threads:[~2022-05-11 16:57 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=20220511165653.GG27195@magnolia \
--to=djwong@kernel.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 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).