On Fri, 2006-01-06 at 11:48 +0000, Russell King wrote: > The scsi_driver business looks like being a pig to solve - so can > SCSI folk please look at what's required to unuse these fields. Well, not necessarily pig. Perhaps piglet. We definitely need the separate probe, shutdown and remove methods for each of our ULDs. However, if they moved into the bus, since scsi_driver is always of type scsi_bus, we could add separate probe, shutdown and remove fields to struct scsi_driver and have the new fields in scsi_bus call those. I have to ask, though; isn't that primarily what most other bus types are going to be doing anyway? So doesn't it make sense to leave the fields in the generic driver? Then the rule becomes that if the bus has the field, we call it, and the bus routine *may* call the corresponding generic driver field if it feels like it. Otherwise if the bus has no callbacks, just use the generic driver ones? James - : 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
