All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: time to move fs/bio.c to block/ ?
Date: Mon, 19 May 2014 15:25:19 +0100	[thread overview]
Message-ID: <20140519142519.GI18016@ZenIV.linux.org.uk> (raw)
In-Reply-To: <537A11CC.5060708@kernel.dk>

On Mon, May 19, 2014 at 08:14:36AM -0600, Jens Axboe wrote:
> On 05/19/2014 08:13 AM, Christoph Hellwig wrote:
> > I recently saw patches to fs/bio.c that were sent to Al instead of Jens.
> > I think having bio.c in fs/ is rather confusing, so maybe it's time to
> > include the simple git-mv for it in the your for-next tree?
> 
> Sure, I've been thinking that too for a while. I'll do the move.

While you are at it, could you take bio-integrity.c with it?  _That_
has zero excuse being anywhere in fs/* - not even "filesystem code
uses quite a few functions from that sucker" as with bio.c.
FWIW, consider the move ACKed.

  reply	other threads:[~2014-05-19 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 14:13 time to move fs/bio.c to block/ ? Christoph Hellwig
2014-05-19 14:14 ` Jens Axboe
2014-05-19 14:25   ` Al Viro [this message]
2014-05-19 14:31     ` Christoph Hellwig
2014-05-19 14:31     ` Jens Axboe
2014-05-19 14:34       ` Christoph Hellwig
2014-05-19 14:38         ` Jens Axboe
2014-05-19 16:39         ` Al Viro
2014-05-19 16:58           ` Christoph Hellwig
2014-05-19 17:05           ` Jens Axboe
2014-05-20  0:28   ` Ming Lei
2014-05-20  2:00     ` Jens Axboe
2014-05-19 14:28 ` Jianyu Zhan
2014-05-19 14:33   ` Christoph Hellwig

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=20140519142519.GI18016@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-kernel@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 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.