Hello! On 24.07.2020 11:59, Bastien Nocera wrote:
When a new device with a specialised device driver is plugged in, the new driver will be modprobe()'d but the driver core will attach the "generic" driver to the device. After that, nothing will trigger a reprobe when the modprobe()'d device driver has finished initialising, as the device has the "generic" driver attached to it. Trigger a reprobe ourselves when new specialised drivers get registered. Fixes: 88b7381a939d
It's strange that nobody has noticed... you need to cite the commit summary here as well, enclosed into ("").
Signed-off-by: Bastien Nocera <hadess@xxxxxxxxxx>
[...]
diff --git a/drivers/usb/core/driver.c b/drivers/usb/core/driver.c index f81606c6a35b..6731a8e104bc 100644 --- a/drivers/usb/core/driver.c +++ b/drivers/usb/core/driver.c
[...] MBR, Sergei
