diff options
| author | Chris Wilson <[email protected]> | 2016-04-13 17:35:00 +0100 |
|---|---|---|
| committer | Chris Wilson <[email protected]> | 2016-04-14 10:45:40 +0100 |
| commit | 0a793ad34f137f146119ec4a4a90694ccab77ea3 (patch) | |
| tree | a9c9dfcd689a83bd10aa166fbc62bc6d1ff6ceb1 /tools/perf/scripts/python/syscall-counts.py | |
| parent | c02e85a06e191f9888f3d561a39b1dc55e934b3b (diff) | |
drm/i915: Force clean compilation with -Werror
Our driver compiles clean (nowadays thanks to 0day) but for me, at least,
it would be beneficial if the compiler threw an error rather than a
warning when it found a piece of suspect code. (I use this to
compile-check patch series and want to break on the first compiler error
in order to fix the patch.)
v2: Kick off a new "Debugging" submenu for i915.ko
At this point, we applied it to the kernel and promptly kicked it out
again as it broke buildbots (due to a compiler warning on 32bits):
commit 908d759b210effb33d927a8cb6603a16448474e4
Author: Daniel Vetter <[email protected]>
Date: Tue May 26 07:46:21 2015 +0200
Revert "drm/i915: Force clean compilation with -Werror"
v3: Avoid enabling -Werror for allyesconfig/allmodconfig builds, using
COMPILE_TEST as a suitable proxy suggested by Andrew Morton. (Damien)
Only make the option available for EXPERT to reinforce that the option
should not be casually enabled.
Signed-off-by: Chris Wilson <[email protected]>
Cc: Jani Nikula <[email protected]>
Cc: Damien Lespiau <[email protected]>
Reviewed-by: Daniel Vetter <[email protected]>
Link: http://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions