From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Michael Turquette <mturquette@baylibre.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Kevin Smith <kevin.smith@elecsyscorp.com>,
"linux-clk\@vger.kernel.org" <linux-clk@vger.kernel.org>,
"Stephen Boyd" <sboyd@codeaurora.org>
Subject: Re: [PATCH v3 1/2] clk: mvebu: Remove corediv clock from Armada XP
Date: Thu, 18 Feb 2016 18:54:41 +0100 [thread overview]
Message-ID: <87twl5q4ym.fsf@free-electrons.com> (raw)
In-Reply-To: <20160218091105.4a272bf9@free-electrons.com> (Thomas Petazzoni's message of "Thu, 18 Feb 2016 09:11:05 +0100")
Hi Mike,=20
=20
On jeu., f=C3=A9vr. 18 2016, Thomas Petazzoni <thomas.petazzoni@free-elect=
rons.com> wrote:
> Hello,
>
> On Wed, 17 Feb 2016 17:16:30 -0800, Michael Turquette wrote:
>> Quoting Kevin Smith (2016-02-11 08:53:52)
>> > There is no corediv clock on Armada XP, so this is unnecessary.
>> >=20
>> > Signed-off-by: Kevin Smith <kevin.smith@elecsyscorp.com>
>> > Cc: Michael Turquette <mturquette@baylibre.com>
>> > Cc: Stephen Boyd <sboyd@codeaurora.org>
>> > Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>
>> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>>=20
>> Acked-by: Michael Turquette <mturquette@baylibre.com>
>>=20
>> I'm fine to take both patches through the clk tree, or to have them go
>> through arm-soc. Let me know if you have a preference.
>
> I'll let Gregory Clement answer on this one. Since there is no build
> dependency with the stuff planned in arm-soc, I believe it's fine if
> you take them, but I'll let Greg give you the final answer since he is
> taking care of the mvebu stuff going to arm-soc.
Indeed I prefer that you take them in the clock tree.
Thanks,
Gregory
>
> Thanks for the review!
>
> Thomas
> --=20
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
--=20
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2016-02-18 17:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 20:41 [PATCH] clk: mvebu: Require corediv clock for Armada 38x Kevin Smith
2016-02-10 21:28 ` Thomas Petazzoni
2016-02-10 23:38 ` Kevin Smith
2016-02-10 23:40 ` [PATCH v2 1/2] clk: mvebu: Remove corediv clock from Armada XP Kevin Smith
2016-02-10 23:40 ` [PATCH v2 2/2] clk: mvebu: Move corediv config to mvebu config Kevin Smith
2016-02-11 8:16 ` Thomas Petazzoni
2016-02-11 16:01 ` Kevin Smith
2016-02-11 16:04 ` Thomas Petazzoni
2016-02-11 16:10 ` Kevin Smith
2016-02-11 16:53 ` [PATCH v3 1/2] clk: mvebu: Remove corediv clock from Armada XP Kevin Smith
2016-02-11 16:54 ` [PATCH v3 2/2] clk: mvebu: Move corediv config to mvebu config Kevin Smith
2016-02-12 16:28 ` Gregory CLEMENT
2016-02-18 1:16 ` Michael Turquette
2016-02-25 23:06 ` Stephen Boyd
2016-02-12 16:28 ` [PATCH v3 1/2] clk: mvebu: Remove corediv clock from Armada XP Gregory CLEMENT
2016-02-18 1:16 ` Michael Turquette
2016-02-18 8:11 ` Thomas Petazzoni
2016-02-18 17:54 ` Gregory CLEMENT [this message]
2016-02-25 23:06 ` Stephen Boyd
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=87twl5q4ym.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=kevin.smith@elecsyscorp.com \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.