@@ -169,11 +169,11 @@ struct scsi_host_template {
169
169
*
170
170
* Deallocation: If we didn't find any devices at this ID, you will
171
171
* get an immediate call to sdev_destroy(). If we find something
172
- * here then you will get a call to slave_configure (), then the
172
+ * here then you will get a call to sdev_configure (), then the
173
173
* device will be used for however long it is kept around, then when
174
174
* the device is removed from the system (or * possibly at reboot
175
175
* time), you will then get a call to sdev_destroy(). This is
176
- * assuming you implement slave_configure and sdev_destroy.
176
+ * assuming you implement sdev_configure and sdev_destroy.
177
177
* However, if you allocate memory and hang it off the device struct,
178
178
* then you must implement the sdev_destroy() routine at a minimum
179
179
* in order to avoid leaking memory
@@ -211,19 +211,15 @@ struct scsi_host_template {
211
211
* up after yourself before returning non-0
212
212
*
213
213
* Status: OPTIONAL
214
- *
215
- * Note: slave_configure is the legacy version, use sdev_configure for
216
- * all new code. A driver must never define both.
217
214
*/
218
215
int (* sdev_configure )(struct scsi_device * , struct queue_limits * lim );
219
- int (* slave_configure )(struct scsi_device * );
220
216
221
217
/*
222
218
* Immediately prior to deallocating the device and after all activity
223
219
* has ceased the mid layer calls this point so that the low level
224
220
* driver may completely detach itself from the scsi device and vice
225
221
* versa. The low level driver is responsible for freeing any memory
226
- * it allocated in the sdev_init or slave_configure calls.
222
+ * it allocated in the sdev_init or sdev_configure calls.
227
223
*
228
224
* Status: OPTIONAL
229
225
*/
0 commit comments