Mike Christie wrote: > It is not vendor specific but it is driver specific and so we need a way > to route the message to the proper userspace handler for similar reasons > you may need a vendor id? For example qlogic handling may be slightly > different in userspace then broadcom. So what I am saying is I thought > the driver and vendor ids are similar, but vendor id may not work for > iscsi_tcp/iser? For now let's forget this issue. I have been using the sysfs lookup scheme because I thought people would frown on not using sysfs since it was there. If we are allowed to add a vendor or driver id to the event then fc can call it what it wants and base it on the pci naming and iscsi can handle its special cases how it needs to. No reason to force our quirks on you guys :) - To unsubscribe from this list: 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
