| commit | c883ef1b1c998d2d66866772fd0fc34afa45641e | [log] [tgz] |
|---|---|---|
| author | Mika Kuoppala <miku@iki.fi> | Tue Oct 28 17:32:30 2014 +0200 |
| committer | Daniel Vetter <daniel.vetter@ffwll.ch> | Tue Nov 04 23:22:14 2014 +0100 |
| tree | 766e496280517d39062de638aeffd3e4bd97e341 | |
| parent | 49e6bc51bc9e22c8a433ba32a4e45a5818de3850 [diff] |
drm/i915: Redefine WARN_ON to include the condition When looking at the bug report logs with triggered WARN_ON, the person doing bug triaging will have to find exact kernel source and match file/line. Attach the condition that triggered the WARN_ON to kernel log. In most cases the context is self evident and this way we can save developer time. The drawback is ~16kbytes bigger i915.ko Signed-off-by: Mika Kuoppala <miku@iki.fi> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>