Message ID | 20181017152513.136526-1-hare@suse.de (mailing list archive) |
---|---|
Headers | show |
Series | Deprecate DAC960 driver | expand |
On 10/17/18 9:25 AM, Hannes Reinecke wrote: > Hi all, > > as we're trying to get rid of the remaining request_fn drivers here's > a patchset to move the DAC960 driver to the SCSI stack. > As per request from hch I've split up the driver into two new SCSI > drivers called 'myrb' and 'myrs'. > > The 'myrb' driver only supports the earlier (V1) firmware interface, which > doesn't have a SCSI interface for the logical drives; for those I've added > a (pretty rudimentary, admittedly) SCSI translation for them. > > The 'myrs' driver supports the newer (V2) firmware interface, which is > SCSI based and doesn't need the translation layer. > > And the weird proc interface from DAC960 has been converted to sysfs attributes. > > Tested with eXtremeRAID 1100 (for V1 Firmware) and Mylex AcceleRAID 170 > (for V2 Firmware). Applied 3/3 in for-4.20/block
Hannes, > as we're trying to get rid of the remaining request_fn drivers here's > a patchset to move the DAC960 driver to the SCSI stack. As per > request from hch I've split up the driver into two new SCSI drivers > called 'myrb' and 'myrs'. Applied to 4.20/scsi-queue since Jens already dropped the block driver. Have you considered a dummy CONFIG_BLK_DEV_DAC960 config option like we did when we merged mpt2sas and mpt3sas? Also, does MODULE_ALIAS do the right thing when a driver is split into two distinct modules?
On 10/18/18 3:14 AM, Martin K. Petersen wrote: > > Hannes, > >> as we're trying to get rid of the remaining request_fn drivers here's >> a patchset to move the DAC960 driver to the SCSI stack. As per >> request from hch I've split up the driver into two new SCSI drivers >> called 'myrb' and 'myrs'. > > Applied to 4.20/scsi-queue since Jens already dropped the block driver. > > Have you considered a dummy CONFIG_BLK_DEV_DAC960 config option like we > did when we merged mpt2sas and mpt3sas? > No, I haven't, but I should probably do it. Should I fix up the patch or send an additional one? > Also, does MODULE_ALIAS do the right thing when a driver is split into > two distinct modules? > Well, it does; half of the time :-) Personally, I don't think there'll be many users around so I've just added if for completions sake. But I can remove it if you think that'll be more suitable. Cheers, Hannes
Hannes, > No, I haven't, but I should probably do it. Should I fix up the patch > or send an additional one? Additional, please. >> Also, does MODULE_ALIAS do the right thing when a driver is split >> into two distinct modules? >> > Well, it does; half of the time :-) Is this a qualified guess or have you actually tried? > Personally, I don't think there'll be many users around so I've just > added if for completions sake. Yeah, I agree it's less critical than mpt[23]sas. However, I'm sure we'll break something for someone somewhere.