From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 5/6] ARM: dts: enable clock support for Broadcom Cygnus
Date: Thu, 18 Jun 2015 13:42:23 -0700 [thread overview]
Message-ID: <55832D2F.7060408@gmail.com> (raw)
In-Reply-To: <20150618195155.9112.72056@quantum>
On 18/06/15 12:51, Michael Turquette wrote:
> Quoting Ray Jui (2015-05-05 11:13:22)
>> Replace current device tree dummy clocks with real clock support for
>> Broadcom Cygnus SoC
>>
>> Signed-off-by: Ray Jui <rjui@broadcom.com>
>> Reviewed-by: Scott Branden <sbranden@broadcom.com>
>
> Patches 1-4 & 6 are applied to clk-next. You can add my Ack to this
> patch:
>
> Acked-by: Michael Turquette <mturquette@baylibre.com>
>
> arm-soc guys,
>
> Any chance you can pick this up? Alternatively I can take it through the
> clk tree with an Ack.
Applied to devicetree/next, thanks!
--
Florian
next prev parent reply other threads:[~2015-06-18 20:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 18:13 [PATCH v7 0/6] Add common clock support for Broadcom iProc architecture Ray Jui
2015-05-05 18:13 ` [PATCH v7 1/6] clk: iproc: define Broadcom iProc clock binding Ray Jui
2015-05-05 18:13 ` [PATCH v7 2/6] clk: iproc: add initial common clock support Ray Jui
2015-05-05 18:13 ` [PATCH v7 3/6] clk: Change bcm clocks build dependency Ray Jui
2015-05-05 18:13 ` [PATCH v7 4/6] clk: cygnus: add clock support for Broadcom Cygnus Ray Jui
2015-05-05 18:13 ` [PATCH v7 5/6] ARM: dts: enable " Ray Jui
2015-06-18 19:51 ` Michael Turquette
2015-06-18 20:42 ` Florian Fainelli [this message]
2015-05-05 18:13 ` [PATCH v7 6/6] clk: cygnus: remove Cygnus dummy clock binding Ray Jui
2015-05-11 21:23 ` [PATCH v7 0/6] Add common clock support for Broadcom iProc architecture Ray Jui
2015-05-13 18:00 ` Florian Fainelli
2015-05-25 17:33 ` Ray Jui
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=55832D2F.7060408@gmail.com \
--to=f.fainelli@gmail.com \
--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).