From: Rob Herring <robh@kernel.org>
To: Kaihua Zhong <zhongkaihua@huawei.com>
Cc: mturquette@baylibre.com, sboyd@codeaurora.org,
mark.rutland@arm.com, xuwei5@hisilicon.com,
catalin.marinas@arm.com, will.deacon@arm.com,
xuejiancheng@hisilicon.com, wenpan@hisilicon.com,
leo.yan@linaro.org, zhangfei.gao@linaro.org,
guodong.xu@linaro.org, chenjun14@huawei.com,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, suzhuangluan@hisilicon.com,
xuezhiliang@hisilicon.com, kevin.wangtao@hisilicon.com
Subject: Re: [PATCH 1/3] dt-bindings: clk: Hi3660: Document stub clock
Date: Mon, 6 Nov 2017 16:13:37 -0600 [thread overview]
Message-ID: <20171106221337.grwywvxzes7jcgob@rob-hp-laptop> (raw)
In-Reply-To: <1509693907-90682-2-git-send-email-zhongkaihua@huawei.com>
On Fri, Nov 03, 2017 at 03:25:05PM +0800, Kaihua Zhong wrote:
> From: Leo Yan <leo.yan@linaro.org>
>
> Document the DT binding for stub clock which is used for CPU,
> GPU and DDR frequency scaling.
>
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
> ---
> Documentation/devicetree/bindings/clock/hi3660-clock.txt | 6 ++++++
> 1 file changed, 6 insertions(+)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-11-06 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 7:25 [PATCH 0/3] Hi3660 stubclock drivers Kaihua Zhong
2017-11-03 7:25 ` [PATCH 1/3] dt-bindings: clk: Hi3660: Document stub clock Kaihua Zhong
2017-11-06 22:13 ` Rob Herring [this message]
2017-11-07 7:54 ` Leo Yan
2017-11-03 7:25 ` [PATCH 2/3] clk: hisilicon: Add support for Hi3660 stub clocks Kaihua Zhong
[not found] ` <1509693907-90682-3-git-send-email-zhongkaihua-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-11-03 17:37 ` Julien Thierry
[not found] ` <f67c976f-12bc-185b-fe12-6a8e761dc392-5wv7dgnIgG8@public.gmane.org>
2017-11-10 4:08 ` Leo Yan
2017-11-06 22:15 ` Rob Herring
2017-11-03 7:25 ` [PATCH 3/3] arm64: dts: Hi3660: Add binding for stub clock Kaihua Zhong
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=20171106221337.grwywvxzes7jcgob@rob-hp-laptop \
--to=robh@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chenjun14@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=guodong.xu@linaro.org \
--cc=kevin.wangtao@hisilicon.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=suzhuangluan@hisilicon.com \
--cc=wenpan@hisilicon.com \
--cc=will.deacon@arm.com \
--cc=xuejiancheng@hisilicon.com \
--cc=xuezhiliang@hisilicon.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangfei.gao@linaro.org \
--cc=zhongkaihua@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