From: Vladimir Zapolskiy <vz@mleia.com>
To: Sylvain Lemieux <slemieux.tyco@gmail.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: mturquette@baylibre.com, stigge@antcom.de, linux-clk@vger.kernel.org
Subject: Re: [PATCH] clk: lpc32xx: do not prepare clock "0"
Date: Wed, 10 Feb 2016 01:45:10 +0200 [thread overview]
Message-ID: <56BA7A06.4020807@mleia.com> (raw)
In-Reply-To: <1455048667.19294.5.camel@localhost>
Hi Sylvain,
On 09.02.2016 22:11, Sylvain Lemieux wrote:
> On Tue, 2016-02-09 at 11:03 -0800, Stephen Boyd wrote:
>> On 02/09, slemieux.tyco@gmail.com wrote:
>>> From: Sylvain Lemieux <slemieux@tycoint.com>
>>>
>>> The following errors are display in the console during the power-on:
>>> [ 0.000000] lpc32xx_usb_clk_init: failed to register (null) clock: -12
>>> [ 0.000000] lpc32xx_clk_init: failed to register (null) clock: -12
>>>
>>> There is no need to prepare clock "0"; the first clock used is 1;
>>>
>>> Signed-off-by: Sylvain Lemieux <slemieux@tycoint.com>
>>> ---
>>
>> Do you mean register instead of prepare? Change looks ok
>> otherwise.
>>
> Should read register in the description;
> I will submit a new version of the patch tomorrow.
>
thanks for catching this leftover after renumbering clocks starting from 1.
Feel free to add to v2
Acked-by: Vladimir Zapolskiy <vz@mleia.com>
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2016-02-09 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 18:29 [PATCH] clk: lpc32xx: do not prepare clock "0" slemieux.tyco
2016-02-09 19:03 ` Stephen Boyd
2016-02-09 20:11 ` Sylvain Lemieux
2016-02-09 23:45 ` Vladimir Zapolskiy [this message]
2016-02-10 0:19 ` 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=56BA7A06.4020807@mleia.com \
--to=vz@mleia.com \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=slemieux.tyco@gmail.com \
--cc=stigge@antcom.de \
/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