On 3/24/24 16:54, Christoph Hellwig wrote:
This is a version of ->slave_configure that also takes a queue_limits structure that the caller applies, and thus allows drivers to reconfigure the queue using the atomic queue limits API. In the long run it should also replace ->slave_configure entirely as there is no need to have two different methods here, and the slave name in addition to being politically charged also has no basis in the SCSI standards or the kernel code.
There are two methods with names that are politically charged: slave_configure() and slave_alloc(). Shouldn't both be renamed?
* Status: OPTIONAL + * + * Note: slave_configure is the legacy version, use device_configure for + * all new code. */ + int (* device_configure)(struct scsi_device *, struct queue_limits *lim); int (* slave_configure)(struct scsi_device *);
The name "device_configure" may make people wonder whether that method perhaps configures a struct device instance. How about using the name "sdev_configure" instead of "device_configure" to make it more clear that this method is used to configure a SCSI device? Thanks, Bart.
