From: "J. Neuschäfer" <j.ne@posteo.net>
To: Brian Masney <bmasney@redhat.com>
Cc: j.ne@posteo.net, Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Tao Lan <taolan@huawei.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] clk: hisilicon: Improve deallocation in error path
Date: Thu, 05 Mar 2026 09:02:11 +0000 [thread overview]
Message-ID: <aalGkLuM1jK3Vlrw@probook> (raw)
In-Reply-To: <aahI_4lfMdQjZCu3@redhat.com>
On Wed, Mar 04, 2026 at 10:00:15AM -0500, Brian Masney wrote:
> On Tue, Mar 03, 2026 at 04:25:18PM +0100, J. Neuschäfer via B4 Relay wrote:
> > From: "J. Neuschäfer" <j.ne@posteo.net>
> >
> > Unmap 'base' if an error occurs after it has been mapped.
> >
> > Reported-by: Tao Lan <taolan@huawei.com>
> > Closes: https://lore.kernel.org/lkml/ZNlSH+eWV8Sk3FYn@probook/
> > Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
>
> My understanding is that you need to use your full first name in the
> Signed-off-by.
I have been contributing to the Linux kernel and other projects using my
abbreviated first name for over a year. It has been mostly well received.
>
> > ---
> > Changes in v2:
> > - Rebase on v7.0-rc2
> > - Update my email address
> > - Reword the commit message somewhat
> > - Link to v1: https://lore.kernel.org/r/20240708-hisi-error-v1-1-727bc7399b63@gmx.net
> > ---
> > drivers/clk/hisilicon/clk.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/clk/hisilicon/clk.c b/drivers/clk/hisilicon/clk.c
> > index fae65127cd4aa8..08050ff1c8cf9a 100644
> > --- a/drivers/clk/hisilicon/clk.c
> > +++ b/drivers/clk/hisilicon/clk.c
> > @@ -70,7 +70,7 @@ struct hisi_clock_data *hisi_clk_init(struct device_node *np,
> >
> > clk_data = kzalloc_obj(*clk_data);
> > if (!clk_data)
> > - goto err;
> > + goto err_base;
> >
> > clk_data->base = base;
> > clk_table = kzalloc_objs(*clk_table, nr_clks);
> > @@ -83,6 +83,8 @@ struct hisi_clock_data *hisi_clk_init(struct device_node *np,
> > return clk_data;
> > err_data:
> > kfree(clk_data);
> > +err_base:
> > + iounmap(base);
>
> Use devm_of_iomap() and it will be automatically cleaned up for you.
This would require a larger restructuring of the HiSilicon clock drivers
to pass a struct device * to hisi_clk_init. I'd rather avoid that
because I can't currently test these drivers and because the benefit is
questionable. However, I still had the upstreaming of this patch in my
backlog, and I think it's simple enough to review as is.
For instance, in drivers/clk/hisilicon/clk-hi3620.c:
static void __init hi3620_clk_init(struct device_node *np)
{
struct hisi_clock_data *clk_data;
clk_data = hisi_clk_init(np, HI3620_NR_CLKS);
...
}
CLK_OF_DECLARE(hi3620_clk, "hisilicon,hi3620-clock", hi3620_clk_init);
Init functions registered with CLK_OF_DECLARE don't have access to a
struct device *.
Best regards,
J. Neuschäfer
next prev parent reply other threads:[~2026-03-05 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 15:25 [PATCH v2] clk: hisilicon: Improve deallocation in error path J. Neuschäfer via B4 Relay
2026-03-04 15:00 ` Brian Masney
2026-03-05 9:02 ` J. Neuschäfer [this message]
2026-03-05 11:11 ` Brian Masney
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=aalGkLuM1jK3Vlrw@probook \
--to=j.ne@posteo.net \
--cc=bmasney@redhat.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=taolan@huawei.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