On Fri, Jan 12, 2018 at 10:50 PM, Olof Johansson <olof@xxxxxxxxx> wrote:
> On Fri, Jan 12, 2018 at 12:45 PM, Rob Herring <robh+dt@xxxxxxxxxx> wrote:
>> On Fri, Jan 12, 2018 at 12:23 PM, Olof Johansson <olof@xxxxxxxxx> wrote:
>> I have more dtc checks in the works (nothing for 4.16 :) ). I'd like
>> the process to work better. I'm not going to fix all the warnings. I
>> don't think Arnd should either. Turning them off by default hasn't
>> worked great either. For some, I'm not sure we can ever get to warning
>> free, but I'd like new stuff to have warnings enabled and no one
>> builds with W=1. We could put together tooling to just show new
>> warnings, but someone has to run it and enforce it. I could stick dtc
>> updates into linux-next for multiple cycles before sending to Linus.
>
> I'll split up and report DT warnings separate from compiler, seems
> like a reasonable approach.
Maybe also report any other output from the build process as another
category. When things build fine, we should see no output at all.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
