All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Nick Piggin <npiggin@suse.de>
Cc: Jeff Garzik <jeff@garzik.org>,
	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:56 +0000	[thread overview]
Message-ID: <20090225154856.GO28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20090225105338.GH22785@wotan.suse.de>

On Wed, Feb 25, 2009 at 11:53:38AM +0100, Nick Piggin wrote:

> If you have a look at it, it's all dealing with buffercache and
> filesystem metadata I think. So I think fs/block_dev.c is the
> right place for it.

There are bits of fs/block_dev.c that belong in block/*; not all of
it, though.

  reply	other threads:[~2009-02-25 15:49 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 [this message]
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=20090225154856.GO28946@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 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.