On Wed, Nov 29, 2006 at 09:13:35AM -0500, James Smart wrote:
> would it only go in include/scsi if it intends to be an exported
> api for LLDD's and/or user apps ? and stay in drivers/scsi if its
> an internal api within the scsi subsystem itself ?
It isn't clear to me that's the intended use of include/scsi. If it is,
it's already being violated, eg by
$ find * -type f |xargs grep scsi_host_scan_allowed
drivers/scsi/scsi_scan.c: if (scsi_host_scan_allowed(shost))
drivers/scsi/scsi_scan.c: if (scsi_host_scan_allowed(shost))
drivers/scsi/scsi_scan.c: if (scsi_host_scan_allowed(shost)) {
drivers/scsi/scsi_scan.c: if (!scsi_host_scan_allowed(shost))
include/scsi/scsi_host.h: * scsi_host_scan_allowed - Is scanning of this
host allowed
include/scsi/scsi_host.h:static inline int scsi_host_scan_allowed(struct
Scsi_Host *shost)
(a good candidate to be moved to scsi_scan.c, in fact!)
scsi_host_state_name, scsi_normalize_sense, scsi_reset_provider,
scsi_test_unit_ready, scsi_put_command are all in similar usage to
scsi_schedule_eh. There's probably more, I just picked some likely
looking candidates.
-
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
