From: Kevin Hilman <khilman@baylibre.com>
To: Michael Turquette <mturquette@baylibre.com>
Cc: "Neil Armstrong" <narmstrong@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, sboyd@codeaurora.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/3] ARM64: dts: meson-gxbb: Add GXBB AO Clock and Reset node
Date: Mon, 29 Aug 2016 12:37:37 -0500 [thread overview]
Message-ID: <m260qjjx26.fsf@baylibre.com> (raw)
In-Reply-To: <147208015014.66208.14165603610884470316@resonance> (Michael Turquette's message of "Wed, 24 Aug 2016 16:09:10 -0700")
Michael Turquette <mturquette@baylibre.com> writes:
> Quoting Kevin Hilman (2016-08-19 15:03:06)
>> Neil Armstrong <narmstrong@baylibre.com> writes:
>>
>> > Add the AO clock controller node for the AmLogic GXBB SoC.
>> >
>> > Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>> > ---
>>
>> Applying this to the amlogic tree, but will need to wait a cycle due to
>> include dependencies on the bindings, which are going through the clock
>> tree.
>
> FYI, for picked patches, Stephen and I create a stable branch for each
> platform. You can pull this into your tree if you want, just let us know
> so we'll be sure not to rebase:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-meson-gxbb-ao
>
OK, I'll be using clk-meson-gxb and clk-meson-gxbb-ao.
Thanks,
Kevin
prev parent reply other threads:[~2016-08-29 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 10:08 [PATCH v2 0/3] clk: Add Meson GXBB Always-On Reset + Clocks Neil Armstrong
2016-08-18 10:08 ` [PATCH v2 1/3] clk: meson: Add GXBB AO Clock and Reset controller driver Neil Armstrong
2016-08-19 19:51 ` Stephen Boyd
2016-08-18 10:08 ` [PATCH v2 2/3] dt-bindings: clock: reset: Add GXBB AO Clock and Reset Bindings Neil Armstrong
2016-08-19 19:51 ` Stephen Boyd
2016-08-18 10:08 ` [PATCH v2 3/3] ARM64: dts: meson-gxbb: Add GXBB AO Clock and Reset node Neil Armstrong
2016-08-19 22:03 ` Kevin Hilman
2016-08-24 23:09 ` Michael Turquette
2016-08-29 17:37 ` Kevin Hilman [this message]
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=m260qjjx26.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=sboyd@codeaurora.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).