Jonathan Toppins schreef op di 17-03-2015 om 22:05 [-0400]:
> Some slight background on these patches, they were born out of the team
> here wanting to have a simple way of easily catching warnings during
> driver development. This seemed like the least cumbersome way. I
> understand if defaulting to yes is not advisable.
>
> Will be happy to submit another patch defaulting to no and clean-up the
> Dots in the paragraphs. From the comments provided so far this approach
> would seem to address them, unless I am misunderstanding and in fact the
> general idea of compiling with -Werror is not wanted.
>
> Appreciate the discussion.
The builds are rather silent as is. Warnings already tend to stand out.
But to follow up on Michal's suggestion, every now and then I do
grep ":[[:digit:]]\+:" $LOG
to catch all well behaved warnings. (I typed that from memory, so the
pattern might be wrong.) The occasional
make $SOME_TARGET > /dev/null
does wonders too.
And, on a general note, the warnings spotting real issues get fixed
quite quickly. The warnings that actually do make it into releases are
almost always false positives. They might only get fixed if someone
finds a way to redo the code in such a way that the compiler has less
trouble analyzing it.
Thanks,
Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
