Roland Dreier wrote:
It's a problem because SRP and iSER are straddling both the SCSI and IB worlds. Probably the best policy is to cc all relevant mailing lists (at least linux-scsi and openib-general) whenever there's a doubt about who should see something.
We are monitoring linux-scsi for tracking iscsi upstream updates.
As far as merging patches goes, I've been merging SRP changes directly to Linus, except for generic fixes to <scsi/srp.h>, which I've been sending through James. Or felt that iSCSI should be merged through my tree, but I have no problem if in the future patches bypass my tree. (But I would like to be cc'ed on changes to IB stuff, especially core things outside of specific drivers)
At this point, we prefer that iser related updates/merges would go through Roland, the IB maintainer, if this poses a problem for scsi/iscsi updates we are open to send our updates/merges via the scsi maintainer.
Or. - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
