All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: virtualization@lists.linux-foundation.org
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Hank Janssen <hjanssen@microsoft.com>,
	"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>,
	"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: hv block drivers
Date: Mon, 30 Aug 2010 21:18:59 +0200	[thread overview]
Message-ID: <201008302119.00069.arnd@arndb.de> (raw)
In-Reply-To: <4C7BEBE7.8060502@goop.org>

On Monday 30 August 2010 19:35:35 Jeremy Fitzhardinge wrote:
>  On 08/30/2010 10:31 AM, Hank Janssen wrote:
> > For a more general question, When/if we make it out of staging, where should these drivers live?
> >
> >       drivers/hyper-v or drivers/scsi and drivers/ide.
> >
> > Is there a standard that is being followed?
> 
> If they're not actually scsi/ide subsystem drivers, then drivers/block
> would seem like the best place (and drivers/ide is truly ancient stuff,
> I think).

Agreed, although I was suggesting to make them SCSI drivers, so they
would go to drivers/scsi/ or a subdirectory of it in that case.

	Arnd

  reply	other threads:[~2010-08-30 19:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 14:43 hv block drivers Arnd Bergmann
2010-08-30 16:17 ` Jeremy Fitzhardinge
2010-08-30 17:08   ` Arnd Bergmann
2010-08-30 17:31     ` Hank Janssen
2010-08-30 17:35       ` Jeremy Fitzhardinge
2010-08-30 19:18         ` Arnd Bergmann [this message]
2010-08-31 10:46           ` Alexander Graf

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=201008302119.00069.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=Xen-devel@lists.xensource.com \
    --cc=hjanssen@microsoft.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=virtualization@lists.osdl.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.