From: Christoph Hellwig <hch@lst.de>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: cluster-devel@redhat.com, Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v9 1/5] iomap: add private pointer to struct iomap
Date: Tue, 19 Jun 2018 08:29:38 +0200 [thread overview]
Message-ID: <20180619062938.GB24513@lst.de> (raw)
In-Reply-To: <20180615121922.13237-2-agruenba@redhat.com>
On Fri, Jun 15, 2018 at 02:19:18PM +0200, Andreas Gruenbacher wrote:
> Add a private pointer to struct iomap to allow filesystems to pass data
> from iomap_begin to iomap_end. Will be used by gfs2 for passing on the
> on-disk inode buffer head.
>
> Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2018-06-19 6:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 12:19 [PATCH v9 0/5] gfs2 iomap write support Andreas Gruenbacher
2018-06-15 12:19 ` [PATCH v9 1/5] iomap: add private pointer to struct iomap Andreas Gruenbacher
2018-06-18 15:25 ` Andreas Gruenbacher
2018-06-19 6:29 ` Christoph Hellwig [this message]
2018-06-15 12:19 ` [PATCH v9 2/5] gfs2: iomap buffered write support Andreas Gruenbacher
2018-06-19 6:36 ` Christoph Hellwig
2018-06-15 12:19 ` [PATCH v9 3/5] gfs2: gfs2_extent_length cleanup Andreas Gruenbacher
2018-06-15 12:19 ` [PATCH v9 4/5] gfs2: iomap direct I/O support Andreas Gruenbacher
2018-06-19 6:42 ` Christoph Hellwig
2018-06-20 16:00 ` Andreas Gruenbacher
2018-06-15 12:19 ` [PATCH v9 5/5] gfs2: Remove gfs2_write_{begin,end} Andreas Gruenbacher
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=20180619062938.GB24513@lst.de \
--to=hch@lst.de \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-fsdevel@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).