After thinking about this a little more - most vendor apps will have already perused sysfs to find the adapters they care about. If so, they already have the host no to vendor mapping. So why pass the vendor id ? It's for the scenario in which someone is logging event messages for later, and may not have the sysfs tree present. Hmmm... implies the logging app, to be really useful, should also log the syfs to host_no relation as part of it's start up. It's a good question/discussion, but it hasn't changed my position: - for generic/well-known transport events, no vendor id is needed - for vendor-specific events, supply vendor id. -- james s - 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
