From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] clk: hisilicon: add CRG driver for Hi3516CV300 SoC
Date: Thu, 20 Oct 2016 10:48:05 -0700 [thread overview]
Message-ID: <20161020174805.GA26139@codeaurora.org> (raw)
In-Reply-To: <5dc55eef-808e-fa78-a5a0-4fccb31e5ceb@hisilicon.com>
On 10/19, Jiancheng Xue wrote:
>
> I'm pretty sure that the patch was sent to the DT list devicetree at vger.kernel.org.
> You had asked a question about "hi3798cv200-sysctrl" and I replied (https://lkml.org/lkml/2016/10/10/517).
> I'm waiting for your new comments. If there's some misunderstatnding, please let me know.
>
Are there two patch series that touch the same clk binding
document? Can you please combine them and resend them if that's
the case?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-10-20 17:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 12:07 [PATCH 0/3] add basic SoC support for HiSilicon Hi3516CV300 Pan Wen
2016-10-17 12:07 ` [PATCH 1/3] arm: hisi: add ARCH_MULTI_V5 support Pan Wen
2016-10-17 13:48 ` Arnd Bergmann
2016-11-16 8:56 ` wenpan
2016-11-16 9:31 ` Wei Xu
2016-11-17 3:03 ` Jiancheng Xue
2016-11-18 6:42 ` Jiancheng Xue
2016-12-05 2:03 ` Jiancheng Xue
2016-12-09 15:07 ` Marty Plummer
2016-12-12 7:11 ` Jiancheng Xue
[not found] ` <59a9b91c-d7be-cf3a-d461-252cb493d61c@gmail.com>
2017-01-20 1:47 ` Jiancheng Xue
2017-01-27 16:44 ` Arnd Bergmann
2016-10-17 12:07 ` [PATCH 2/3] clk: hisilicon: add CRG driver for Hi3516CV300 SoC Pan Wen
2016-10-18 15:58 ` Rob Herring
2016-10-19 2:38 ` Jiancheng Xue
2016-10-19 2:45 ` Rob Herring
2016-10-19 3:54 ` Jiancheng Xue
2016-10-20 17:48 ` Stephen Boyd [this message]
2016-10-21 1:46 ` Jiancheng Xue
2016-10-17 12:07 ` [PATCH 3/3] dts: hisi: add dts files for Hi3516CV300 demo board Pan Wen
2016-12-12 11:34 ` Jiancheng Xue
2017-01-20 16:40 ` Wei Xu
2017-01-22 9:33 ` Kefeng Wang
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=20161020174805.GA26139@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).