From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jeff Garzik <jeff@garzik.org>
Cc: Nick Piggin <npiggin@suse.de>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [patch][rfc] fs: move bdev code out of buffer.c
Date: Wed, 25 Feb 2009 15:48:10 +0000 [thread overview]
Message-ID: <20090225154810.GN28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <49A51EFF.4020600@garzik.org>
On Wed, Feb 25, 2009 at 05:35:43AM -0500, Jeff Garzik wrote:
> Nick Piggin wrote:
>> Move some block device related code out from buffer.c and put it in
>> block_dev.c. I'm trying to move non-buffer_head code out of buffer.c
>>
>> Is this OK?
>>
>> ---
>> fs/block_dev.c | 146 ++++++++++++++++++++++++++++++++++++++++++++
>> fs/buffer.c | 145 -------------------------------------------
>> include/linux/buffer_head.h | 7 --
>> include/linux/fs.h | 7 ++
>> 4 files changed, 153 insertions(+), 152 deletions(-)
>
> If you are going to churn all this old code, maybe the blkdev stuff better
> belongs in block/ dir?
Some of it... BTW, so does fs/partitions/* stuff. I'll resurrect the
patch taking that crap over to block/*.
next prev parent reply other threads:[~2009-02-25 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 9:44 [patch][rfc] fs: move bdev code out of buffer.c Nick Piggin
2009-02-25 10:35 ` Jeff Garzik
2009-02-25 10:53 ` Nick Piggin
2009-02-25 15:48 ` Al Viro
2009-02-25 15:48 ` Al Viro [this message]
2009-02-25 15:47 ` 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=20090225154810.GN28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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).