All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Tyler Baker <tyler.baker@linaro.org>
Cc: "Dinh Nguyen" <dinguyen@opensource.altera.com>,
	"Mike Turquette" <mturquette@linaro.org>,
	dinh.linux@gmail.com, linux-clk@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Maxime Ripard" <maxime.ripard@free-electrons.com>,
	"Emilio López" <emilio@elopez.com.ar>
Subject: Re: [PATCHv2 5/6] clk: sunxi: make use of of_clk_parent_fill helper function
Date: Tue, 21 Jul 2015 11:00:47 -0700	[thread overview]
Message-ID: <55AE88CF.5040407@codeaurora.org> (raw)
In-Reply-To: <CANMBJr5FCib=+JG9hdGehbxhayFDkTp341mNCnFTiS0GpGxZZw@mail.gmail.com>

On 07/21/2015 09:29 AM, Tyler Baker wrote:
> Hi Dinh,
>
> On 21 July 2015 at 08:22, Dinh Nguyen <dinguyen@opensource.altera.com> wrote:
>> On Tue, 21 Jul 2015, Tyler Baker wrote:
>>
>>> Hi,
>>>
>>> On 17 July 2015 at 17:53, Stephen Boyd <sboyd@codeaurora.org> wrote:
>>>> On 07/06, dinguyen@opensource.altera.com wrote:
>>>>> From: Dinh Nguyen <dinguyen@opensource.altera.com>
>>>>>
>>>>> Use of_clk_parent_fill to fill in the parent clock names' array.
>>>>>
>>>>> Signed-off-by: Dinh Nguyen <dinguyen@opensource.altera.com>
>>>>> Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
>>>>> Cc: "Emilio López" <emilio@elopez.com.ar>
>>>>> ---
>>>> Applied to clk-next with that fix I posted.
>>> The kernelci.org bot reported sunxi a20 boot failures[1][2] in
>>> next-20150720 and next-20150721. I have bisected[3] these failures to
>>> this commit. However, I have not investigated any further but
>>> reverting this commit on top of next-20150721 gets the boards booting
>>> again.
>>>
>> Can you please try this patch?
> I've tested the patch below on top of next-20150721 and can confirm it
> fixes the sunxi a20 issues I've reported.

Thanks both. I've squashed this in and pushed it out to clk-next.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-07-21 18:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  3:59 [PATCHv2 0/6] clk: make use of of_clk_parent_fill helper function dinguyen
2015-07-07  3:59 ` [PATCHv2 1/6] clk: at91: " dinguyen
2015-07-18  0:52   ` Stephen Boyd
2015-07-07  3:59 ` [PATCHv2 2/6] clk: qoriq: " dinguyen
2015-07-18  0:52   ` Stephen Boyd
2015-07-07  3:59 ` [PATCHv2 3/6] clk: keystone: " dinguyen
2015-07-18  0:52   ` Stephen Boyd
2015-07-07  3:59 ` [PATCHv2 4/6] clk: st: " dinguyen
2015-07-18  0:52   ` Stephen Boyd
2015-07-07  3:59 ` [PATCHv2 5/6] clk: sunxi: " dinguyen
2015-07-07  5:07   ` Maxime Ripard
2015-07-18  0:52   ` Stephen Boyd
2015-07-18  0:53   ` Stephen Boyd
2015-07-21 14:42     ` Tyler Baker
2015-07-21 14:42       ` Tyler Baker
2015-07-21 15:22       ` Dinh Nguyen
2015-07-21 16:29         ` Tyler Baker
2015-07-21 16:29           ` Tyler Baker
2015-07-21 18:00           ` Stephen Boyd [this message]
2015-07-07  3:59 ` [PATCHv2 6/6] clk: ti: " dinguyen
2015-07-18  0:52   ` 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=55AE88CF.5040407@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=dinguyen@opensource.altera.com \
    --cc=dinh.linux@gmail.com \
    --cc=emilio@elopez.com.ar \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=mturquette@linaro.org \
    --cc=tyler.baker@linaro.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 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.