Dear Chander Kashyap,
On 06/09/13 13:32, Chander Kashyap wrote:
Hi Albert,
On 5 September 2013 18:58, Albert ARIBAUD albert.u.boot@aribaud.net wrote:
Hi Chander,
On Thu, 5 Sep 2013 17:36:34 +0530, Chander Kashyap chander.kashyap@linaro.org wrote:
Hi Albert,
On 5 September 2013 17:08, Albert ARIBAUD albert.u.boot@aribaud.net wrote:
Hi Chander,
On Thu, 5 Sep 2013 16:47:27 +0530, Chander Kashyap chander.kashyap@linaro.org wrote:
Hi Lukasz,
On 5 September 2013 16:27, Lukasz Majewski l.majewski@samsung.com wrote:
Hi Chander,
>> >> Its working for me. >> But my dtc -v: "Version: DTC 1.3.0" >>
Have you managed to properly build test Samsung's u-boot tree with DTC 1.3.0?
Yes, I am able to build and test. I am running on ubuntu.
Then you are not testing on a recent enough U-Boot source tree; currently, master (and arm) require dtc version >= 1.4.0, and will fail as indicated by Lukasz and as experienced by me -- I had to build dtc version 1.4.0 from git source.
Sorry for big mess. I had re-based my tree to u-boot samsung. I have tested it after re-basing to u-boot tree. It was failing.
Shall i send all the patches again, or is it possible to send the single failing patch.
Well, if you have rebased to u-boot-master, then you can as well do an interactive rebase so that the commit which breaks builds is omitted.
Offending patch was part of two patch series. I have fixed it and resend it with series again.
Since the patchset is already applied to u-boot-samsung, If you send new patchset, then I should do rebase and forced push. If possible please send fixing patch instead of new patchset.
Thanks, Minkyu Kang.