[GIT PULL] ARM: mvebu: DT fixes for v3.14

Olof Johansson olof at lixom.net
Wed Feb 19 11:25:15 EST 2014


On Wed, Feb 19, 2014 at 7:43 AM, Jason Cooper <jason at lakedaemon.net> wrote:
> On Tue, Feb 18, 2014 at 04:24:46PM -0800, Olof Johansson wrote:
>> On Tue, Feb 18, 2014 at 11:11:02AM -0500, Jason Cooper wrote:
>> > All,
>> >
>> > I've been sitting on the missing alias for a while waiting for more DT
>> > fixes to show up.  Well, finally one did. :(
>> >
>> > Please pull for v3.14.
>> >
>> > I intend to re-add the dove PMU node once I know for certain the
>> > corresponding driver is going in to v3.15 (pull request already sent).
>>
>> I've pulled this, but:
>>
>> > Jason Cooper (1):
>> >       ARM: dove: dt: revert PMU interrupt controller node
>>
>> Hmm. Seems like my dove machine (cubox) still booted. This does fix the
>> boot time warning though.
>
> ok, this was a compound error on my part.  The reported WARN_ON kernel
> logs stopped after the WARN_ON output.  I assumed the board hung at that
> point.  Second, I've been too focused on the d*mn phy failures in the
> bootfarm I haven't even looked at the cubox booting successfully.

No worries.

> At any rate, it does remove the warning for v3.14, and the driver is
> slated for v3.15, So I'll re-add the node for v3.15.
>
> Unfortunately, this creates a dependency on mvebu/dt-fixes by mvebu/dt.
> Or, I could just add the node to fixes-non-critical for v3.15 to avoid
> the dependency.  Which do you prefer?

Just base mvebu/dt on top of dt-fixes, alternatively merge dt-fixes
into dt before you have to apply the conflicting patches -- that
should take care of it. Or am I missing something here?


-Olof



More information about the linux-arm-kernel mailing list