| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <DA48E656-CCCF-4B2B-B930-8AAB92E08108@suse.de> Date: Tue, 31 Aug 2010 12:46:30 +0200 From: Alexander Graf <agraf@...e.de> To: Arnd Bergmann <arnd@...db.de> Cc: virtualization@...ts.linux-foundation.org, "Xen-devel@...ts.xensource.com" <Xen-devel@...ts.xensource.com>, Stefano Stabellini <stefano.stabellini@...citrix.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "'virtualization@...ts.osdl.org'" <virtualization@...ts.osdl.org> Subject: Re: hv block drivers 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists