From: Herve Codina <herve.codina@bootlin.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Saravana Kannan <saravanak@google.com>,
linux-kernel@vger.kernel.org,
Allan Nielsen <allan.nielsen@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Steen Hegelund <steen.hegelund@microchip.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v3 1/1] driver core: Keep the supplier fwnode consistent with the device
Date: Mon, 8 Jan 2024 14:23:02 +0100 [thread overview]
Message-ID: <20240108142302.7ecd2705@bootlin.com> (raw)
In-Reply-To: <2024010436-bulb-direness-5582@gregkh>
Hi Greg,
On Thu, 4 Jan 2024 16:39:49 +0100
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> On Tue, Nov 14, 2023 at 08:46:32AM +0100, Herve Codina wrote:
> > The commit 3a2dbc510c43 ("driver core: fw_devlink: Don't purge child
> > fwnode's consumer links") introduces the possibility to use the
> > supplier's parent device instead of the supplier itself.
> > In that case the supplier fwnode used is not updated and is no more
> > consistent with the supplier device used.
> >
> > Use the fwnode consistent with the supplier device when checking flags.
> >
> > Fixes: 3a2dbc510c43 ("driver core: fw_devlink: Don't purge child fwnode's consumer links")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Herve Codina <herve.codina@bootlin.com>
> > ---
> > Changes v2 -> v3:
> > Do not update the supplier handle in order to keep the original handle
> > for debug traces.
> >
> > Changes v1 -> v2:
> > Remove sup_handle check and related pr_debug() call as sup_handle cannot be
> > invalid if sup_dev is valid.
> >
> > drivers/base/core.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/base/core.c b/drivers/base/core.c
> > index 4d8b315c48a1..440b52ec027f 100644
> > --- a/drivers/base/core.c
> > +++ b/drivers/base/core.c
> > @@ -2082,7 +2082,7 @@ static int fw_devlink_create_devlink(struct device *con,
> > * supplier device indefinitely.
> > */
> > if (sup_dev->links.status == DL_DEV_NO_DRIVER &&
> > - sup_handle->flags & FWNODE_FLAG_INITIALIZED) {
> > + sup_dev->fwnode->flags & FWNODE_FLAG_INITIALIZED) {
> > dev_dbg(con,
> > "Not linking %pfwf - dev might never probe\n",
> > sup_handle);
> > --
> > 2.41.0
> >
>
> Is this still needed? If so, how come no one is noticing it?
>
I think it is. At least, I don't see anything that make this patch obsolete.
Hervé
next prev parent reply other threads:[~2024-01-08 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 7:46 [PATCH v3 1/1] driver core: Keep the supplier fwnode consistent with the device Herve Codina
2024-01-04 15:39 ` Greg Kroah-Hartman
2024-01-08 13:23 ` Herve Codina [this message]
2024-03-19 14:55 ` Herve Codina
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=20240108142302.7ecd2705@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=horatiu.vultur@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
--cc=stable@vger.kernel.org \
--cc=steen.hegelund@microchip.com \
--cc=thomas.petazzoni@bootlin.com \
/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;
as well as URLs for NNTP newsgroup(s).