I tested that Chris tree does not have problem.
It's caused by IMX tree updates.
Chris,
Is the way Shawn suggested OK for you?
Regards
Dong Aisheng
On Tue, Dec 17, 2013 at 11:16 AM, Shawn Guo <shawn.guo@xxxxxxxxxx> wrote:
> Hi Chris,
>
> Please drop fc4fafac9656 ("ARM: dts: sabresd: add usdhc4 support") from
> your tree. It should go via my tree (with a rebase). Sorry, I did not
> notice it early.
>
> Shawn
>
> On Tue, Dec 17, 2013 at 11:07:19AM +0800, Dong Aisheng wrote:
>> Hi Stephen,
>>
>> Sorry, i just see this mail.
>> It seems the imx pinctrl dt binding has changes since Chris pick my patch.
>> I will fix it ASAP.
>>
>> Regards
>> Dong Aisheng
>>
>> On Tue, Dec 17, 2013 at 10:28 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
>> > Hi Chris,
>> >
>> > ping?
>> >
>> > On Fri, 13 Dec 2013 12:57:16 +1100 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
>> >>
>> >> After merging the mmc tree, today's linux-next build (arm
>> >> multi_v7_defconfig) failed like this:
>> >>
>> >> ERROR (phandle_references): Reference to non-existent node or label "pinctrl_usdhc4_1"
>> >>
>> >> ERROR: Input tree has errors, aborting (use -f to force output)
>> >> make[2]: *** [arch/arm/boot/dts/imx6dl-sabresd.dtb] Error 2
>> >> ERROR (phandle_references): Reference to non-existent node or label "pinctrl_usdhc4_1"
>> >>
>> >> ERROR: Input tree has errors, aborting (use -f to force output)
>> >> make[2]: *** [arch/arm/boot/dts/imx6q-sabresd.dtb] Error 2
>> >>
>> >> Caused by commit fc4fafac9656 ("ARM: dts: sabresd: add usdhc4 support").
>> >>
>> >> I have used the mmc tree from next-20131212 for today.
>> >
>> > --
>> > Cheers,
>> > Stephen Rothwell sfr@xxxxxxxxxxxxxxxx
>
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
