From: Christoph Hellwig <hch@infradead.org>
To: Josef Bacik <jbacik@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, hch@infradead.org
Subject: Re: [RFC][PATCH] expose get_block via inode_operations
Date: Wed, 23 Apr 2008 03:35:17 -0400 [thread overview]
Message-ID: <20080423073517.GA19338@infradead.org> (raw)
In-Reply-To: <20080422181824.GA2852@unused.rdu.redhat.com>
No thanks. Just add a generic_fiemap which takes a get_block paramter
ala
static int
ext2_fiemap(struct inode *inode, ...)
{
return generic_fiemap(inode, ...., ext2_get_block);
}
To keep the abstractions clear. That's how we do it for all other
get_block users already.
next prev parent reply other threads:[~2008-04-23 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 18:18 [RFC][PATCH] expose get_block via inode_operations Josef Bacik
2008-04-23 7:35 ` Christoph Hellwig [this message]
2008-04-23 13:05 ` Josef Bacik
2008-04-23 7:59 ` Al Viro
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=20080423073517.GA19338@infradead.org \
--to=hch@infradead.org \
--cc=jbacik@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).