From: Stephen Boyd <sboyd@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: Jiancheng Xue <xuejiancheng@hisilicon.com>,
mturquette@baylibre.com, mark.rutland@arm.com,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, bin.chen@linaro.org,
elder@linaro.org, hermit.wangheming@hisilicon.com,
yanhaifeng@hisilicon.com, wenpan@hisilicon.com
Subject: Re: [RESEND PATCH v2] clk: hisilicon: add CRG driver for Hi3798CV200 SoC
Date: Thu, 27 Oct 2016 17:25:48 -0700 [thread overview]
Message-ID: <20161028002548.GN26139@codeaurora.org> (raw)
In-Reply-To: <20161027134833.vdtd5t5hx33o3ahb@rob-hp-laptop>
On 10/27, Rob Herring wrote:
> On Fri, Oct 21, 2016 at 09:37:10AM +0800, Jiancheng Xue wrote:
> > Add CRG driver for Hi3798CV200 SoC. CRG(Clock and Reset
> > Generator) module generates clock and reset signals used
> > by other module blocks on SoC.
> >
> > Signed-off-by: Jiancheng Xue <xuejiancheng@hisilicon.com>
> > ---
> > change log
> > v2:
> > - Fixed compiling error when compiled as a module.
> > - Fixed issues pointed by Stephen Boyd.
> > - Added prefix HISTB for clock index macro definitions.
>
> What Stephen asked for is send this and the Hi3516CV300 series as one
> series since there is a dependency.
Exactly. Please resend both parts, along with Rob's ack on this
one. I can review it all then and hopefully Rob will be ok with
the other binding change.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-10-28 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 1:37 [RESEND PATCH v2] clk: hisilicon: add CRG driver for Hi3798CV200 SoC Jiancheng Xue
[not found] ` <1477013830-11481-1-git-send-email-xuejiancheng-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2016-10-27 13:48 ` Rob Herring
2016-10-28 0:25 ` Stephen Boyd [this message]
[not found] ` <20161028002548.GN26139-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-10-28 1:19 ` Jiancheng Xue
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=20161028002548.GN26139@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bin.chen@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@linaro.org \
--cc=hermit.wangheming@hisilicon.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=wenpan@hisilicon.com \
--cc=xuejiancheng@hisilicon.com \
--cc=yanhaifeng@hisilicon.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;
as well as URLs for NNTP newsgroup(s).