On Wed, Apr 28, 2021 at 11:00:05AM -0300, Jason Gunthorpe wrote: > I thought about doing it like that, it is generally a good idea, > however, if I add new API surface to the driver core I really want to > get rid of device_bind_driver(), or at least most of its users. > > I'm pretty sure Greg will ask for it too. > > So, I need a way to sequence that which doesn't mean I have to shelf > the mdev stuff for ages while I try to get acks from lots of places. > > Leave this alone and fix it after? Export device_driver_attach() and > say to try and fix the rest after? Maybe. Or convert one or two samples. > I think this will still need the ugly errno capture though.. Why?
