From: Stephen Boyd <sboyd@codeaurora.org>
To: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, ralf@linux-mips.org,
mturquette@baylibre.com, devicetree@vger.kernel.org,
linux-mips@linux-mips.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, paul@crapouillou.net,
malat@debian.org, dom.peklo@gmail.com
Subject: Re: [RFC 2/4] clk: Add Ingenic X1000 CGU driver
Date: Wed, 25 Oct 2017 02:23:30 -0700 [thread overview]
Message-ID: <20171025092330.GD30645@codeaurora.org> (raw)
In-Reply-To: <20170927151527.25570-3-prasannatsmkumar@gmail.com>
On 09/27, PrasannaKumar Muralidharan wrote:
> Add support for the clocks provided by CGU in Ingenic X1000 SoC.
>
> Signed-off-by: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
> ---
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:[~2017-10-25 9:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 15:15 [RFC 0/4] Add Ingenic X1000 SoC Support PrasannaKumar Muralidharan
2017-09-27 15:15 ` [RFC 1/4] dt-bindings: Add Ingenic X1000 SoC clock define PrasannaKumar Muralidharan
2017-09-27 15:15 ` [RFC 2/4] clk: Add Ingenic X1000 CGU driver PrasannaKumar Muralidharan
2017-10-25 9:23 ` Stephen Boyd [this message]
2017-09-27 15:15 ` [RFC 3/4] MIPS: Ingenic: Initial X1000 SoC support PrasannaKumar Muralidharan
2018-03-06 0:08 ` James Hogan
2018-03-07 13:44 ` PrasannaKumar Muralidharan
2018-03-07 14:19 ` Jiaxun Yang
2018-03-07 15:21 ` PrasannaKumar Muralidharan
2018-03-07 14:35 ` James Hogan
2018-03-07 15:05 ` PrasannaKumar Muralidharan
2018-03-07 15:10 ` James Hogan
2018-03-07 15:22 ` PrasannaKumar Muralidharan
2018-03-07 15:52 ` Jiaxun Yang
2018-03-07 16:25 ` PrasannaKumar Muralidharan
2018-03-07 18:13 ` Mathieu Malaterre
2018-03-10 19:05 ` Jiaxun Yang
2018-03-09 0:52 ` Jiaxun Yang
2017-09-27 15:15 ` [RFC 4/4] MIPS: Ingenic: Add Halley2 development board support PrasannaKumar Muralidharan
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=20171025092330.GD30645@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dom.peklo@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=malat@debian.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=paul@crapouillou.net \
--cc=prasannatsmkumar@gmail.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.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).