From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rob Herring <robh@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] driver core: Refactor device unbind/probe fail clean-ups
Date: Thu, 24 Feb 2022 10:08:58 +0100 [thread overview]
Message-ID: <YhdLKuv3D/tQ9ia8@kroah.com> (raw)
In-Reply-To: <20220223225257.1681968-1-robh@kernel.org>
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 :(
thanks,
greg k-h
next prev parent reply other threads:[~2022-02-24 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 22:52 [PATCH 0/2] driver core: Refactor device unbind/probe fail clean-ups Rob Herring
2022-02-23 22:52 ` [PATCH 1/2] driver core: Refactor multiple copies of device cleanup Rob Herring
2022-02-23 22:52 ` [PATCH 2/2] driver core: Refactor sysfs and drv/bus remove hooks Rob Herring
2022-02-24 9:07 ` Greg Kroah-Hartman
2022-02-24 9:08 ` Greg Kroah-Hartman [this message]
2022-02-24 13:24 ` [PATCH 0/2] driver core: Refactor device unbind/probe fail clean-ups Rob Herring
2022-02-24 18:24 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YhdLKuv3D/tQ9ia8@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox