All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Jeff Garzik <jeff@garzik.org>, Matthew Wilcox <matthew@wil.cx>,
	scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v3] block: move RAID transport class to BLOCK menu
Date: Thu, 6 Mar 2008 19:29:54 +0100	[thread overview]
Message-ID: <20080306182953.GI17940@kernel.dk> (raw)
In-Reply-To: <1204819346.3062.19.camel@localhost.localdomain>

On Thu, Mar 06 2008, James Bottomley wrote:
> On Thu, 2008-03-06 at 07:28 +0100, Jens Axboe wrote:
> > On Wed, Mar 05 2008, Randy Dunlap wrote:
> > > On Sun, 4 Nov 2007 12:17:27 -0800 Randy Dunlap wrote:
> > > 
> > > ping.  James, Jens?
> > 
> > Fine with me, though it's really up to James to pass judgement on this.
> 
> In principle, yes, when (if) it's actually made useful, it would belong
> at the block layer (or even in misc or the md/dm layer), but while it's
> a bit vestigial, there's not really much point in moving it.  I'll tie a
> knot in my hankie to see if I can make it progress and then we can see
> where it should go.

I mistakenly thought that the md raid stuff was already moved over,
since the patch to move the transport was suggested. If it isn't and
SCSI is still the sole user of that code, then by all means keep it
there. Once patches for md or eg cciss or other block raid controllers
are supplied, then it'll make sense to move the transport class.

IOW, I completely agree with you James and thought we were further ahead
than we really are :-)

-- 
Jens Axboe


      reply	other threads:[~2008-03-06 18:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-04 18:44 [PATCH] scsi menu: move RAID transport class to Transports menu Randy Dunlap
2007-11-04 18:58 ` Matthew Wilcox
2007-11-04 19:00   ` Jeff Garzik
2007-11-04 19:39     ` [PATCH v2] block: move RAID transport class to BLOCK menu Randy Dunlap
2007-11-04 19:58       ` Jeff Garzik
2007-11-04 20:02         ` Randy Dunlap
2007-11-04 20:06           ` Jeff Garzik
2007-11-04 20:12             ` Randy Dunlap
2007-11-04 20:17             ` [PATCH v3] " Randy Dunlap
2007-11-04 20:19               ` Jeff Garzik
2008-03-06  3:08               ` Randy Dunlap
2008-03-06  6:28                 ` Jens Axboe
2008-03-06 16:02                   ` James Bottomley
2008-03-06 18:29                     ` Jens Axboe [this message]

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=20080306182953.GI17940@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jeff@garzik.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=randy.dunlap@oracle.com \
    /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.