From: Jeff Garzik <jeff@garzik.org>
To: Nick Piggin <npiggin@suse.de>
Cc: 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 05:35:43 -0500 [thread overview]
Message-ID: <49A51EFF.4020600@garzik.org> (raw)
In-Reply-To: <20090225094419.GF22785@wotan.suse.de>
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?
Jeff
next prev parent reply other threads:[~2009-02-25 10:36 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 [this message]
2009-02-25 10:53 ` Nick Piggin
2009-02-25 15:48 ` Al Viro
2009-02-25 15:48 ` Al Viro
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=49A51EFF.4020600@garzik.org \
--to=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 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.