From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Cc: Brian Foster <bfoster@redhat.com>
Subject: [ANNOUNCE] xfs-linux: iomap-for-next updated to 6e552494fb90
Date: Tue, 4 May 2021 09:26:27 -0700 [thread overview]
Message-ID: <20210504162627.GA8582@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.
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. This is just removing io_private now that we're into
the second week of the merge window and nobody suddenly wanted to use
it.
The new head of the iomap-for-next branch is commit:
6e552494fb90 iomap: remove unused private field from ioend
New Commits:
Brian Foster (1):
[6e552494fb90] iomap: remove unused private field from ioend
Code Diffstat:
fs/iomap/buffered-io.c | 7 +------
fs/xfs/xfs_aops.c | 2 +-
include/linux/iomap.h | 5 +----
3 files changed, 3 insertions(+), 11 deletions(-)
reply other threads:[~2021-05-04 16:26 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=20210504162627.GA8582@magnolia \
--to=djwong@kernel.org \
--cc=bfoster@redhat.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 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).