From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/3] gfs2: More iomap enablement
Date: Mon, 9 Jul 2018 08:47:28 -0400 (EDT) [thread overview]
Message-ID: <1196157821.48705557.1531140448231.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180707093904.23177-1-agruenba@redhat.com>
Hi Andreas,
----- Original Message -----
> Andreas Gruenbacher (3):
> gfs2: fallocate_chunk: Always initialize struct iomap
> gfs2: Use iomap for stuffed direct I/O reads
> gfs2: use iomap_readpage for blocksize == PAGE_SIZE
These three look good to me. Feel free to add my Reviewed-by.
Bob Peterson
prev parent reply other threads:[~2018-07-09 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 9:39 [Cluster-devel] [PATCH 0/3] gfs2: More iomap enablement Andreas Gruenbacher
2018-07-07 9:39 ` [Cluster-devel] [PATCH 1/3] gfs2: fallocate_chunk: Always initialize struct iomap Andreas Gruenbacher
2018-07-07 9:39 ` [Cluster-devel] [PATCH 2/3] gfs2: Use iomap for stuffed direct I/O reads Andreas Gruenbacher
2018-07-07 9:39 ` [Cluster-devel] [PATCH 3/3] gfs2: use iomap_readpage for blocksize == PAGE_SIZE Andreas Gruenbacher
2018-07-09 12:47 ` Bob Peterson [this message]
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=1196157821.48705557.1531140448231.JavaMail.zimbra@redhat.com \
--to=rpeterso@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).