public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Lin <shawn.lin@kernel-upstream.org>
To: "Heiko Stübner" <heiko@sntech.de>,
	"Shawn Lin" <shawn.lin@rock-chips.com>
Cc: Xing Zheng <zhengxing@rock-chips.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH 3/7] clk: rockchip: release io resource when rk3036_clk_init failed
Date: Sun, 13 Mar 2016 09:49:40 +0800	[thread overview]
Message-ID: <56E4C734.6010702@kernel-upstream.org> (raw)
In-Reply-To: <8447746.miDbEHA5rR@diego>

在 2016/3/13 0:48, Heiko Stübner 写道:
> Hi Shawn,
>
> Am Sonntag, 13. März 2016, 00:25:25 schrieb Shawn Lin:
>> We should call iounmap to relase reg_base since it's not going
>> to be used any more.
>>
>> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
>
> I see that change for rk3036, rk3188(+rk3066) and rk3368.
> But it looks like rk3228 and rk3288 should also get that, or am I just
> overlooking something?

My fault, we need to do that for 3228/3288 as well.
Sorry for my slippy finger. I assign wrong patch-numbers to my
script.

I will squash up patch[3/7],[4/7],[5/7] as well as for 3228/3288, and
resend a separate patch for it.

>
> Also, I think we can fold these changes into one patch, as it's the completely
> same addition for all clock-drivers.
>
>
> Heiko
>
>> ---
>>
>>   drivers/clk/rockchip/clk-rk3036.c | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/clk/rockchip/clk-rk3036.c
>> b/drivers/clk/rockchip/clk-rk3036.c index 8c683cc..284c36f 100644
>> --- a/drivers/clk/rockchip/clk-rk3036.c
>> +++ b/drivers/clk/rockchip/clk-rk3036.c
>> @@ -453,6 +453,7 @@ static void __init rk3036_clk_init(struct device_node
>> *np) ctx = rockchip_clk_init(np, reg_base, CLK_NR_CLKS);
>>   	if (IS_ERR(ctx)) {
>>   		pr_err("%s: rockchip clk init failed\n", __func__);
>> +		iounmap(reg_base);
>>   		return;
>>   	}
>
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>

  reply	other threads:[~2016-03-13  1:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-12 16:24 [PATCH 0/7] Some trivial patches for rockchip clk stuff Shawn Lin
2016-03-12 16:25 ` [PATCH 1/7] clk: rockchip: remove mux_core_reg from rockchip_cpuclk_reg_data Shawn Lin
2016-03-14  0:13   ` Heiko Stuebner
2016-03-12 16:25 ` [PATCH 2/7] clk: rockchip: fix warning reported by kernel-doc Shawn Lin
2016-03-14  0:25   ` Heiko Stuebner
2016-03-12 16:25 ` [PATCH 3/7] clk: rockchip: release io resource when rk3036_clk_init failed Shawn Lin
2016-03-12 16:48   ` Heiko Stübner
2016-03-13  1:49     ` Shawn Lin [this message]
2016-03-12 16:25 ` [PATCH 4/7] clk: rockchip: release io resource when rk3188_common_clk_init failed Shawn Lin
2016-03-12 16:25 ` [PATCH 5/7] clk: rockchip: release io resource when rk3368_clk_init failed Shawn Lin
2016-03-12 16:25 ` [PATCH 6/7] clk: rockchip: remove redundant checking of device_node Shawn Lin
2016-03-14  0:26   ` Heiko Stuebner
2016-03-12 16:26 ` [PATCH 7/7] clk: rockchip: fix a typo for rockchip_rk3399_pll_set_params Shawn Lin
2016-03-12 16:45   ` Heiko Stübner

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=56E4C734.6010702@kernel-upstream.org \
    --to=shawn.lin@kernel-upstream.org \
    --cc=heiko@sntech.de \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=zhengxing@rock-chips.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