Messages in this thread | | | Date | Thu, 24 Feb 2022 19:24:55 +0100 | From | Greg Kroah-Hartman <> | Subject | Re: [PATCH 0/2] driver core: Refactor device unbind/probe fail clean-ups |
| |
On Thu, Feb 24, 2022 at 07:24:48AM -0600, Rob Herring wrote: > On Thu, Feb 24, 2022 at 3:09 AM Greg Kroah-Hartman > <gregkh@linuxfoundation.org> wrote: > > > > On Wed, Feb 23, 2022 at 04:52:55PM -0600, Rob Herring wrote: > > > The same sequences of device clean-up code are duplicated 3 times. > > > Changes to this code are prone to missing one of the copies. This > > > series refactors the code into 2 common functions as there's some slight > > > differences in the intermediate steps. > > > > > > Rob > > > > > > Rob Herring (2): > > > driver core: Refactor multiple copies of device cleanup > > > driver core: Refactor sysfs and drv/bus remove hooks > > > > > > drivers/base/dd.c | 80 ++++++++++++++++++----------------------------- > > > 1 file changed, 30 insertions(+), 50 deletions(-) > > > > > > -- > > > 2.32.0 > > > > > > > What branch/tree did you make these against? They do not apply at all > > to my "driver-core-next" branch of the driver-core.git tree on > > git.kernel.org :( > > linux-next. It is dependent on commit d8f7a5484f21 ("driver core: Free > DMA range map when device is released") in your driver-core-linus > branch.
Ah, my fault, I'll wait for the branch to be merged and then apply these next week.
thanks,
greg k-h
| |