From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2: iomap-write patches pushed to for-next
Date: Mon, 2 Jul 2018 17:46:12 +0200 [thread overview]
Message-ID: <20180702154612.14147-1-agruenba@redhat.com> (raw)
Hi,
the following patches for gfs2 iomap write support have been pushed to
the gfs2 for-next branch. The gfs2 for-next branch can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/log/?h=for-next
This (partially) depends on the iomap-4.19-merge branch in the xfs repository:
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/log/?h=iomap-4.19-merge
Thanks,
Andreas
Andreas Gruenbacher (5):
gfs2: Further iomap cleanups
gfs2: iomap buffered write support
gfs2: gfs2_extent_length cleanup
gfs2: iomap direct I/O support
gfs2: Remove gfs2_write_{begin,end}
fs/gfs2/aops.c | 331 ++--------------------------------------
fs/gfs2/aops.h | 19 +++
fs/gfs2/bmap.c | 398 ++++++++++++++++++++++++++++++++++++++++---------
fs/gfs2/file.c | 162 ++++++++++++++++++--
4 files changed, 510 insertions(+), 400 deletions(-)
create mode 100644 fs/gfs2/aops.h
reply other threads:[~2018-07-02 15:46 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=20180702154612.14147-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
/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).