aboutsummaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorJames Bottomley <James.Bottomley@steeleye.com>2005-08-14 17:09:01 -0500
committerJames Bottomley <jejb@mulgrave.(none)>2005-08-14 17:21:27 -0500
commitd0a7e574007fd547d72ec693bfa35778623d0738 (patch)
tree3457bdf4e8eaf870971aab03c99c31534ba85658 /kernel
parent10c1b88987d618f4f89c10e11e574c76de73b5e7 (diff)
downloadkernel_samsung_espresso10-d0a7e574007fd547d72ec693bfa35778623d0738.zip
kernel_samsung_espresso10-d0a7e574007fd547d72ec693bfa35778623d0738.tar.gz
kernel_samsung_espresso10-d0a7e574007fd547d72ec693bfa35778623d0738.tar.bz2
[SCSI] correct transport class abstraction to work outside SCSI
I recently tried to construct a totally generic transport class and found there were certain features missing from the current abstract transport class. Most notable is that you have to hang the data on the class_device but most of the API is framed in terms of the generic device, not the class_device. These changes are two fold - Provide the class_device to all of the setup and configure APIs - Provide and extra API to take the device and the attribute class and return the corresponding class_device Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions