From: Cristian Marussi <cristian.marussi@arm.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Cristian Marussi <cristian.marussi@arm.com>,
Sudeep Holla <sudeep.holla@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] firmware: arm_scmi: Use common error handling code in __scmi_device_create()
Date: Thu, 11 Jun 2026 12:20:33 +0100 [thread overview]
Message-ID: <aiqZiv995sbvcBjq@pluto> (raw)
In-Reply-To: <545ffb86-55f5-46b2-83ca-285cd8d540d7@web.de>
On Thu, Jun 11, 2026 at 10:34:52AM +0200, Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Thu, 11 Jun 2026 10:27:45 +0200
>
> Use an additional label so that a bit of exception handling can be better
> reused at the end of an if branch.
>
Hi,
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> ---
> drivers/firmware/arm_scmi/bus.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/firmware/arm_scmi/bus.c b/drivers/firmware/arm_scmi/bus.c
> index 793be9eabaed..8c20ed1a8243 100644
> --- a/drivers/firmware/arm_scmi/bus.c
> +++ b/drivers/firmware/arm_scmi/bus.c
> @@ -450,14 +450,13 @@ __scmi_device_create(struct device_node *np, struct device *parent,
> return NULL;
>
> scmi_dev->name = kstrdup_const(name ?: "unknown", GFP_KERNEL);
> - if (!scmi_dev->name) {
> - kfree(scmi_dev);
> - return NULL;
> - }
> + if (!scmi_dev->name)
> + goto free_scmi_dev;
>
> id = ida_alloc_min(&scmi_bus_id, 1, GFP_KERNEL);
> if (id < 0) {
> kfree_const(scmi_dev->name);
> +free_scmi_dev:
> kfree(scmi_dev);
I can understand the aim, but jumping in the middle of another block
just to reuse the cleanup statement is far less readable (and ugly)
Cleanup handlers probably a better solution here...but I have NOT looked
at all the sorrounding code here recently...so I maybe wrong and keeping
the current code could be even bette.
Thanks,
Cristian
prev parent reply other threads:[~2026-06-11 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 8:34 [PATCH] firmware: arm_scmi: Use common error handling code in __scmi_device_create() Markus Elfring
2026-06-11 11:20 ` Cristian Marussi [this message]
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=aiqZiv995sbvcBjq@pluto \
--to=cristian.marussi@arm.com \
--cc=Markus.Elfring@web.de \
--cc=arm-scmi@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@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 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.