From: "Heiko Stübner" <heiko@sntech.de>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: mturquette@baylibre.com, sboyd@codeaurora.org,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-clk@vger.kernel.org, huangtao@rock-chips.com,
xxx@rock-chips.com, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/5] clk: rockchip: fix up the clk for RK3368 SoC
Date: Fri, 10 Mar 2017 11:45:36 +0100 [thread overview]
Message-ID: <3564953.RFZXb1jYdB@diego> (raw)
In-Reply-To: <1488884719-10350-1-git-send-email-zhangqing@rock-chips.com>
Am Dienstag, 7. März 2017, 19:05:14 CET schrieb Elaine Zhang:
> change in V2:
> split clock-id addition and the assignment in the clock-
> driver.
>
> Elaine Zhang (5):
> clk: rockchip: rk3368: fix up the timer-ids
> clk: rockchip: rk3368: remove the unused id
folded this into the first patch and added a commit message explaining the
timer-id circumstances
> clk: rockchip: add clock ids for timer10-15 of RK3368 SoCs
> clk: rockchip: rk3368: export SCLK_TIMERXX id for timers
> clk: rockchip: rk3368: add some clks as critical
applied with some minor corrections to the subject (rk3368 in the regular
wording) for 4.12
Thanks
Heiko
prev parent reply other threads:[~2017-03-10 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 11:05 [PATCH v2 0/5] clk: rockchip: fix up the clk for RK3368 SoC Elaine Zhang
2017-03-07 11:05 ` [PATCH v2 1/5] clk: rockchip: rk3368: fix up the timer-ids Elaine Zhang
2017-03-07 11:05 ` [PATCH v2 2/5] clk: rockchip: rk3368: remove the unused id Elaine Zhang
2017-03-07 11:05 ` [PATCH v2 3/5] clk: rockchip: add clock ids for timer10-15 of RK3368 SoCs Elaine Zhang
2017-03-07 11:05 ` [PATCH v2 4/5] clk: rockchip: rk3368: export SCLK_TIMERXX id for timers Elaine Zhang
2017-03-07 11:16 ` [PATCH v2 5/5] clk: rockchip: rk3368: add some clks as critical Elaine Zhang
2017-03-10 10:45 ` Heiko Stübner [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=3564953.RFZXb1jYdB@diego \
--to=heiko@sntech.de \
--cc=huangtao@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=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=xxx@rock-chips.com \
--cc=zhangqing@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