On 26/08/14 17:37, James Bottomley wrote: > On Tue, 2014-08-26 at 16:23 +0200, Juergen Gross wrote: >> On 08/26/2014 04:14 PM, David Vrabel wrote: >>> On 18/08/14 10:31, jgr...@suse.com wrote: >>>> From: Juergen Gross <jgr...@suse.com> >>>> >>>> Add myself as maintainer for the Xen pvSCSI stuff. >>>> >>>> Signed-off-by: Juergen Gross <jgr...@suse.com> >>>> --- >>>> MAINTAINERS | 8 ++++++++ >>>> 1 file changed, 8 insertions(+) >>>> >>>> diff --git a/MAINTAINERS b/MAINTAINERS >>>> index aefa948..360f86f 100644 >>>> --- a/MAINTAINERS >>>> +++ b/MAINTAINERS >>>> @@ -10086,6 +10086,14 @@ S: Supported >>>> F: drivers/block/xen-blkback/* >>>> F: drivers/block/xen* >>>> >>>> +XEN PVSCSI DRIVERS >>>> +M: Juergen Gross <jgr...@suse.com> >>>> +L: xen-de...@lists.xenproject.org (moderated for non-subscribers) >>> >>> You should add the appropriate scsi list here >>> (linux-scsi@vger.kernel.org I presume?) >> >> Really? Xen PCI and Xen Block susbsystems don't have an according entry. >> James, do you have an opinion here? I don't mind adding linux-scsi, but >> I think the Xen list is the appropriate one for pvSCSI. > > It depends how you want to handle this, but the patches have to come on > to the SCSI list somehow. You can have them directly posted by adding > the list, or you can repost them yourselves. It's a question of > workflow.
I think these drivers have had (and will continue to have) the most useful review from scsi people. I think posting directly (hence earlier) to linux-scsi will ensure the best quality. This is the workflow used for the Xen network drivers and I think it works well. David -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
