All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: Amitai Gottlieb <amitaig@hailo.ai>,
	arm-scmi@vger.kernel.org, sudeep.holla@arm.com
Subject: Re: [PATCH] firmware: arm_scmi: Fix unused notifier-block in unregister
Date: Thu, 11 Dec 2025 15:53:37 +0300	[thread overview]
Message-ID: <aTq-0QAUONrNERGA@stanley.mountain> (raw)
In-Reply-To: <aTq2IA6V1nTE-XSC@pluto>

On Thu, Dec 11, 2025 at 12:17:01PM +0000, Cristian Marussi wrote:
> On Thu, Dec 11, 2025 at 01:49:27PM +0200, Amitai Gottlieb wrote:
> > In function `scmi_devm_notifier_unregister` the notifier-block parameter
> > was unused and therefore never passed to `devres_release`. This causes
> > the function to always return -ENOENT and fail to unregister the
> > notifier.
> 
> [ CC-ing also Sudeep ]
> 
> Hi,
> 
> thanks for this.
> 
> LGTM.
> 
> Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>
> 
> > 
> > In drivers that rely on this function for cleanup this causes
> > unexpected failures including kernel-panic.
> > 
> > Fixes: 5ad3d1cf7d34 ("firmware: arm_scmi: Introduce new devres
> > notification ops")

This Fixes tag needs to be all on one line.
Fixes: 5ad3d1cf7d34 ("firmware: arm_scmi: Introduce new devres notification ops")

> > Signed-off-by: Amitai Gottlieb <amitaig@hailo.ai>
> > ---
> > 
> > This is not needed upstream becaues the bug was fixed
> > in a refactor by commit 264a2c520628 ("firmware: arm_scmi: Simplify
> > scmi_devm_notifier_unregister").  It is needed for the 5.15, 6.1 and
> > 6.6 kernels.
> 
> I think there is some sort of syntax to refer to the applicable Kernel
> versions in the tag line....not sure it can be easily followed here...so
> maybe the above comment is enough...
> 
> More details here...
> 
> https://docs.kernel.org/process/stable-kernel-rules.html

I'm pretty sure those little comments aren't parsed automatically...
It feels duplicative.  I don't love those little notes because it feels
like the Fixes tag should normally be sufficient otherwise I want a full
explanation.  There was an embarrassing bug where the notes were wrong
and the patch was missing a Fixes tag so it wasn't backported far enough
in distro kernels.

It can't hurt to add them to the tag section, I suppose.

Cc: <stable@vger.kernel.org> # 5.15.x, 6.1.x, and 6.6.x

Leaving them out is also fine, really.

We definitely still need the note.  I said before that note about
"This is not needed upstream becaues the bug was fixed
in a refactor by commit 264a2c520628 ("firmware: arm_scmi: Simplify
scmi_devm_notifier_unregister")" should go under the --- cut off line,
but actually I think now that it should go into the actual commit
message itself.  Otherwise people who work on distro kernels, for
example, will wonder why the commit doesn't have an upstream hash.

Reviewed-by: Dan Carpenter <dan.carpenter@linaro.org>

Wait until Sudeep has responded, and then resend the patch to
stable@vger.kernel.org with all the Reviewed-by tags.

regards,
dan carpenter


  reply	other threads:[~2025-12-11 12:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 11:49 [PATCH] firmware: arm_scmi: Fix unused notifier-block in unregister Amitai Gottlieb
2025-12-11 12:17 ` Cristian Marussi
2025-12-11 12:53   ` Dan Carpenter [this message]
     [not found]     ` <DB9P194MB13560B1BBAD2A8A8E6260719C1ADA@DB9P194MB1356.EURP194.PROD.OUTLOOK.COM>
2025-12-15 12:19       ` Fw: " amitaigottlieb
2025-12-15 15:13         ` Sudeep Holla
  -- strict thread matches above, loose matches on Subject: below --
2025-12-15 16:37 Amitai Gottlieb
2025-12-15 17:13 ` Sudeep Holla

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=aTq-0QAUONrNERGA@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=amitaig@hailo.ai \
    --cc=arm-scmi@vger.kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=sudeep.holla@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.