From: Christoph Hellwig <hch@infradead.org>
To: Bob Peterson <rpeterso@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.cz>,
Al Viro <viro@ZenIV.linux.org.uk>,
Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [vfs PATCH v3 4/4] GFS2: Use new iomap interface for fiemap
Date: Tue, 15 Mar 2016 00:33:59 -0700 [thread overview]
Message-ID: <20160315073359.GG11669@infradead.org> (raw)
In-Reply-To: <1457122300-28514-5-git-send-email-rpeterso@redhat.com>
> - ret = __generic_block_fiemap(inode, fieinfo, start, len,
> - gfs2_block_map);
> + ret = __generic_iomap_fiemap(inode, fieinfo, start, len,
> + gfs2_get_iomap);
So it seems like the generic_iomap_fiemap you added is unused,
no need to add it then.
prev parent reply other threads:[~2016-03-15 7:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 20:11 [vfs PATCH v3 0/4] vfs: Expand iomap interface to fiemap Bob Peterson
2016-03-04 20:11 ` [vfs PATCH v3 1/4] VFS: move iomap from exportfs.h to iomap.h Bob Peterson
2016-03-15 7:29 ` Christoph Hellwig
2016-03-28 19:53 ` Bob Peterson
2016-03-29 7:40 ` Christoph Hellwig
2016-03-29 22:20 ` Dave Chinner
2016-03-30 6:47 ` Christoph Hellwig
2016-04-07 19:58 ` Bob Peterson
2016-04-07 20:42 ` Christoph Hellwig
2016-04-10 17:15 ` Christoph Hellwig
2016-04-11 6:17 ` Dave Chinner
2016-04-12 18:29 ` Christoph Hellwig
2016-04-13 0:22 ` Dave Chinner
2016-03-04 20:11 ` [vfs PATCH v3 2/4] VFS: Add new __generic_iomap_fiemap interface Bob Peterson
2016-03-07 10:18 ` Jan Kara
2016-03-15 7:33 ` Christoph Hellwig
2016-03-04 20:11 ` [vfs PATCH v3 3/4] GFS2: Add function gfs2_get_iomap Bob Peterson
2016-03-04 20:11 ` [vfs PATCH v3 4/4] GFS2: Use new iomap interface for fiemap Bob Peterson
2016-03-15 7:33 ` Christoph Hellwig [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=20160315073359.GG11669@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rpeterso@redhat.com \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.