From: Alexander Graf <agraf@suse.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: virtualization@lists.linux-foundation.org,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>
Subject: Re: hv block drivers
Date: Tue, 31 Aug 2010 12:46:30 +0200 [thread overview]
Message-ID: <DA48E656-CCCF-4B2B-B930-8AAB92E08108@suse.de> (raw)
In-Reply-To: <201008302119.00069.arnd@arndb.de>
On 30.08.2010, at 21:18, Arnd Bergmann wrote:
> 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.
It's basically the same as the VMware PV SCSI driver, no? And that one is in drivers/scsi/vmw_pvscsi.c.
Alex
prev parent reply other threads:[~2010-08-31 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 14:43 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
2010-08-31 10:46 ` Alexander Graf [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=DA48E656-CCCF-4B2B-B930-8AAB92E08108@suse.de \
--to=agraf@suse.de \
--cc=Xen-devel@lists.xensource.com \
--cc=arnd@arndb.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®