On 04/19/2016 07:01 AM, Heiko Schocher wrote: > Hello Marek, > > Am 18.04.2016 um 19:52 schrieb Marek Vasut: >> On 04/18/2016 05:46 PM, Tom Rini wrote: >>> On Mon, Apr 18, 2016 at 05:37:02PM +0200, Marek Vasut wrote: >>>> On 04/18/2016 05:31 PM, Tom Rini wrote: >>>>> On Fri, Apr 15, 2016 at 12:41:02PM +0200, Heiko Schocher wrote: >>>>> >>>>>> Fix following DTC warnings for all socfpga boards: >>>>> >>>>> We're going to defer on this patch for now, thanks. >>>>> >>>> Can you elaborate please? >>> >>> Yes, I did in another of the threads here (aside, I wish this was done a >>> series and there was a 0/N, but, oh well). We import these from the >>> kernel, as this isn't a U-Boot change, we're the wrong place to start >>> making these changes by and large. In some quick googling around, the >>> various SoC trees are updating to fix these problems and we'll pull them >>> in whenever our relevant custodian is happy. Or when someone can say >>> "resync with $hash from the kernel" and get them Acked-by or whatever. >>> >> You will want to backport this patch, it's in linux-next too: >> >> http://www.spinics.net/lists/linux-kbuild/msg12538.html > > Yes ... we ignore warnings ... maybe an agreement ... > > I can prepare a patch for this, but I prefer to add this build flag > for each arch, so we can at least remove it for each arch, when all > warnings are fixed in linux and we did a sync with linux ... > > Would this be OK?
The patch explains that the warnings of this type are only displayed if you set W=1 or W=2 for the build system. I suspect the DTC is just a bit too eager to display warnings which are not very important. If you want to hunt down warnings, set W=n , no need to introduce another knob :) -- Best regards, Marek Vasut _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
