From: "Heiko Stübner" <heiko@sntech.de>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Lin Huang <hl@rock-chips.com>,
dianders@chromium.org, linux-rockchip@lists.infradead.org,
mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] clk: rockchip: add pclk_pd_pmu to the list of rk3288 critical clocks
Date: Tue, 04 Aug 2015 21:40:16 +0200 [thread overview]
Message-ID: <10063547.S7PvqCkF78@diego> (raw)
In-Reply-To: <55C113CF.2000601@codeaurora.org>
Am Dienstag, 4. August 2015, 12:34:39 schrieb Stephen Boyd:
> On 08/04/2015 01:54 AM, Heiko Stübner wrote:
> > Hi,
> >
> > Am Dienstag, 4. August 2015, 14:41:26 schrieb Lin Huang:
> >
> > I guess this patch then would need a
> >
> > From: Heiko Stuebner <heiko@sntech.de>
> >
> > at this point to override the author then.
>
> Sounds right. Please resend the patch properly. Also, is there a 2/2? I
> never got it.
Patch 2/2 is a pinctrl change, that actually depends in this patch.
Improved clock-handling in the pinctrl driver caused the pd_pmu clock to get
deactivated.
So, perhaps it might be even better to get an Ack from the clock maintainer
and merge both patches through the pinctrl tree?
In which case Linus Walleij should also be included as recipient of this patch
when resending.
next prev parent reply other threads:[~2015-08-04 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 6:41 [PATCH v3 1/2] clk: rockchip: add pclk_pd_pmu to the list of rk3288 critical clocks Lin Huang
2015-08-04 6:41 ` [PATCH v3 2/2] pinctrl: rockchip: only enable gpio clock when it setting Lin Huang
2015-08-04 8:53 ` Heiko Stübner
2015-08-04 8:54 ` [PATCH v3 1/2] clk: rockchip: add pclk_pd_pmu to the list of rk3288 critical clocks Heiko Stübner
2015-08-04 19:34 ` Stephen Boyd
2015-08-04 19:40 ` Heiko Stübner [this message]
2015-08-04 19:44 ` Stephen Boyd
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=10063547.S7PvqCkF78@diego \
--to=heiko@sntech.de \
--cc=dianders@chromium.org \
--cc=hl@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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 \
/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