[PATCH 08/11] drm: Pull the test on drm_debug in the logging macros

2014-03-25 Thread Jani Nikula
On Mon, 24 Mar 2014, Damien Lespiau wrote: > In the logging code, we are currently checking is we need to output in s/is/if/ > drm_ut_debug_printk(). This is too late. The problem is that when we write > something like: > > DRM_DEBUG_DRIVER("ELD on [CONNECTOR:%d:%s], [ENCODER:%d:%s]\n", >

[PATCH 08/11] drm: Pull the test on drm_debug in the logging macros

2014-03-25 Thread Daniel Vetter
On Tue, Mar 25, 2014 at 11:56:24AM +0200, Jani Nikula wrote: > On Mon, 24 Mar 2014, Damien Lespiau wrote: > > In the logging code, we are currently checking is we need to output in > > s/is/if/ > > > drm_ut_debug_printk(). This is too late. The problem is that when we write > > something like: >

[PATCH 08/11] drm: Pull the test on drm_debug in the logging macros

2014-03-24 Thread Damien Lespiau
In the logging code, we are currently checking is we need to output in drm_ut_debug_printk(). This is too late. The problem is that when we write something like: DRM_DEBUG_DRIVER("ELD on [CONNECTOR:%d:%s], [ENCODER:%d:%s]\n", connector->base.id, drm_ge