From: Dongjiu Geng <gengdongjiu@huawei.com>
To: Markus Elfring <Markus.Elfring@web.de>, <linux-clk@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: [PATCH v3] clk: hisilicon: refine hi3620_mmc_clk_init() and fix memory leak issues
Date: Thu, 19 Nov 2020 20:01:22 +0800 [thread overview]
Message-ID: <5b976ad4-43e2-a021-6a93-25642b44cec5@huawei.com> (raw)
In-Reply-To: <ef1eac81-c4f9-ca4d-f056-3cdbddcaad73@web.de>
On 2020/11/19 17:07, Markus Elfring wrote:
>> Refine hi3620_mmc_clk_init() to use of_clk_add_hw_provider()
>> instead of of_clk_add_provider(), …
>
> …
>> +++ b/drivers/clk/hisilicon/clk-hi3620.c
> …
>> @@ -439,17 +440,22 @@ static struct clk *hisi_register_clk_mmc(struct hisi_mmc_clock *mmc_clk,
> …
>> + err = clk_hw_register(NULL, hw);
>> +
>> + if (err) {
>
> I suggest to omit a blank line here.
>
>
> …
>> +++ b/drivers/clk/hisilicon/clk.c
>> @@ -65,25 +65,26 @@ struct hisi_clock_data *hisi_clk_init(struct device_node *np,
> …
>> of_clk_add_provider(np, of_clk_src_onecell_get, &clk_data->clk_data);
>> return clk_data;
>> -err_data:
>> +free_clk_data:
>
> How do you think about to adjust also such a function call for this function implementation?
>
> Will further collateral evolution become interesting?
> https://elixir.bootlin.com/linux/v5.10-rc4/C/ident/of_clk_add_provider
Thanks for the review.
How about we adjust such a function call in another series patches? I suggest do it in another series.
For this patch, how about we firstly merge it after I fix the above comments(omit a blank line)?
>
> Regards,
> Markus
> .
>
next prev parent reply other threads:[~2020-11-19 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 19:22 [PATCH V3] " Dongjiu Geng
2020-11-12 10:59 ` Dongjiu Geng
2020-11-19 4:09 ` Dongjiu Geng
[not found] ` <ef1eac81-c4f9-ca4d-f056-3cdbddcaad73@web.de>
2020-11-19 12:01 ` Dongjiu Geng [this message]
[not found] ` <393a7eca-e6a0-ddf8-e0aa-ca9121acf4f3@web.de>
2020-11-20 3:08 ` [v3] " Dongjiu Geng
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=5b976ad4-43e2-a021-6a93-25642b44cec5@huawei.com \
--to=gengdongjiu@huawei.com \
--cc=Markus.Elfring@web.de \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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
all inboxes | Powered by JetHome®