On Wed, 2020-07-22 at 13:12 +0200, Greg Kroah-Hartman wrote: > On Wed, Jul 22, 2020 at 11:46:27AM +0200, 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. > > > > Signed-off-by: Bastien Nocera <hadess@xxxxxxxxxx> > > --- > > What commit id does this fix? And if it's in an older kernel, should > it > be backported to the stable trees? Fixes: 88b7381a939de0fa1f1b1629c56b03dca7077309 AFAIK, the apple-mfi-fastcharge driver wasn't backported to stable trees, and it's the only driver that's impacted by this bug, so there shouldn't be any need to backport it there. Did you want me to respin it with this info? Cheers
