From: Stephen Boyd <sboyd@codeaurora.org>
To: Shunqian Zheng <zhengsq@rock-chips.com>
Cc: gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org,
maxime.ripard@free-electrons.com, heiko@sntech.de,
caesar.wang@rock-chips.com, mturquette@baylibre.com,
linux-clk@vger.kernel.org, dianders@chromium.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
xjq@rock-chips.com
Subject: Re: [PATCH v2 1/5] clk: rockchip: rk3288: Add the clock id of eFuse
Date: Tue, 11 Aug 2015 18:31:27 -0700 [thread overview]
Message-ID: <20150812013127.GK26614@codeaurora.org> (raw)
In-Reply-To: <1439288024-13359-2-git-send-email-zhengsq@rock-chips.com>
On 08/11, Shunqian Zheng wrote:
> From: ZhengShunQian <zhengsq@rock-chips.com>
>
> The clock id is necessary item, changing it from 0
> then can be referred in driver and device tree.
>
> Signed-off-by: ZhengShunQian <zhengsq@rock-chips.com>
> Reviewed-by: Heiko Stuebner <heiko@sntech.de>
> ---
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-08-12 1:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 10:13 [PATCH v2 0/5] Add eFuse driver of Rockchip SoC Shunqian Zheng
2015-08-11 10:13 ` [PATCH v2 1/5] clk: rockchip: rk3288: Add the clock id of eFuse Shunqian Zheng
2015-08-12 1:31 ` Stephen Boyd [this message]
2015-08-11 10:13 ` [PATCH v2 2/5] nvmem: fix the out-of-range leak in read/write() Shunqian Zheng
2015-08-11 10:13 ` Shunqian Zheng
2015-08-11 10:13 ` [PATCH v2 3/5] nvmem: rockchip-efuse: implement efuse driver Shunqian Zheng
2015-08-11 10:13 ` [PATCH v2 4/5] Documentation: rockchip-efuse: describe the usage of eFuse Shunqian Zheng
2015-08-11 10:13 ` [PATCH v2 5/5] ARM: dts: rockchip: add eFuse config of rk3288 SoC Shunqian Zheng
2015-08-11 10:13 ` Shunqian Zheng
2015-12-12 19:21 ` [PATCH v2 0/5] Add eFuse driver of Rockchip SoC 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=20150812013127.GK26614@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=caesar.wang@rock-chips.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mturquette@baylibre.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=xjq@rock-chips.com \
--cc=zhengsq@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.