From: Nishanth Menon <nm@ti.com>
To: Rob Herring <robh@kernel.org>, Tony Lindgren <tony@atomide.com>
Cc: Tero Kristo <t-kristo@ti.com>, Rhyland Klein <rklein@nvidia.com>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Regression: next-20160518: Clk? on BeagleBoard-X15
Date: Fri, 20 May 2016 14:43:05 -0500 [thread overview]
Message-ID: <573F68C9.2060404@ti.com> (raw)
In-Reply-To: <CAL_Jsq+ORQ5PP80_HbH16+SaHFLdrefcVGFzsvgLYiiwtq9PuQ@mail.gmail.com>
On 05/19/2016 12:35 PM, Rob Herring wrote:
> On Thu, May 19, 2016 at 11:57 AM, Tony Lindgren <tony@atomide.com> wrote:
>> * Nishanth Menon <nm@ti.com> [160519 08:48]:
>>> I have'nt bisected yet, but the platform seems to have booted on
>>> next-20160517
>>> https://github.com/nmenon/kernel-test-logs/blob/next-20160517/omap2plus_defconfig/am57xx-evm.txt
>>>
>>> https://github.com/nmenon/kernel-test-logs/blob/next-20160518/omap2plus_defconfig/am57xx-evm.txt
>>
>> Seems to be commit ac78f9bdcf38 ("drivers/of: Fix depth when
>> unflattening devicetree").
>>
>> Rob, you need to start playing golf or something between -rc6 and
>> the end of the merge window or something :)
>
> It seems the fix for one board broke more... It is fixed in my tree now.
Thanks. Looks good today on my test lists:
https://github.com/nmenon/kernel-test-logs/tree/next-20160520
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression: next-20160518: Clk? on BeagleBoard-X15
Date: Fri, 20 May 2016 14:43:05 -0500 [thread overview]
Message-ID: <573F68C9.2060404@ti.com> (raw)
In-Reply-To: <CAL_Jsq+ORQ5PP80_HbH16+SaHFLdrefcVGFzsvgLYiiwtq9PuQ@mail.gmail.com>
On 05/19/2016 12:35 PM, Rob Herring wrote:
> On Thu, May 19, 2016 at 11:57 AM, Tony Lindgren <tony@atomide.com> wrote:
>> * Nishanth Menon <nm@ti.com> [160519 08:48]:
>>> I have'nt bisected yet, but the platform seems to have booted on
>>> next-20160517
>>> https://github.com/nmenon/kernel-test-logs/blob/next-20160517/omap2plus_defconfig/am57xx-evm.txt
>>>
>>> https://github.com/nmenon/kernel-test-logs/blob/next-20160518/omap2plus_defconfig/am57xx-evm.txt
>>
>> Seems to be commit ac78f9bdcf38 ("drivers/of: Fix depth when
>> unflattening devicetree").
>>
>> Rob, you need to start playing golf or something between -rc6 and
>> the end of the merge window or something :)
>
> It seems the fix for one board broke more... It is fixed in my tree now.
Thanks. Looks good today on my test lists:
https://github.com/nmenon/kernel-test-logs/tree/next-20160520
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2016-05-20 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <573DDFE6.8010209@ti.com>
2016-05-19 16:57 ` Regression: next-20160518: Clk? on BeagleBoard-X15 Tony Lindgren
2016-05-19 16:57 ` Tony Lindgren
2016-05-19 17:35 ` Tomi Valkeinen
2016-05-19 17:35 ` Tomi Valkeinen
2016-05-19 17:35 ` Rob Herring
2016-05-19 17:35 ` Rob Herring
2016-05-20 19:43 ` Nishanth Menon [this message]
2016-05-20 19:43 ` Nishanth Menon
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=573F68C9.2060404@ti.com \
--to=nm@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rklein@nvidia.com \
--cc=robh@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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.