[PATCH] drm: modes: add missing [drm] to message printing

Jani Nikula jani.nikula at linux.intel.com
Thu Feb 4 17:08:39 UTC 2016


On Thu, 04 Feb 2016, Lukas Wunner <lukas at wunner.de> wrote:
> Hi,
>
> On Thu, Feb 04, 2016 at 03:03:52PM +0100, LABBE Corentin wrote:
>> The warning message in drm_mode_parse_command_line_for_connector miss
>> the [drm] at beginning.
>> This patch add it and take the opportunity to convert
>> printk(KERN_WARNING to pr_warn()
>> 
>> Signed-off-by: LABBE Corentin <clabbe.montjoie at gmail.com>
>> ---
>>  drivers/gpu/drm/drm_modes.c | 3 +--
>>  1 file changed, 1 insertion(+), 2 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
>> index 20775c0..f7448a5 100644
>> --- a/drivers/gpu/drm/drm_modes.c
>> +++ b/drivers/gpu/drm/drm_modes.c
>> @@ -1371,8 +1371,7 @@ bool drm_mode_parse_command_line_for_connector(const char *mode_option,
>>  	}
>>  done:
>>  	if (i >= 0) {
>> -		printk(KERN_WARNING
>> -			"parse error at position %i in video mode '%s'\n",
>> +		pr_warn("[drm] parse error at position %i in video mode '%s'\n",
>>  			i, name);
>
> Hm, maybe it's warranted to add a DRM_WARNING macro to include/drm/drmP.h
> and use that instead?

I think it's good as-is for now. We have this all over the place, and
I'd rather see a concerted effort moving away from all this custom stuff
than having a one-off definition for a single patch. And that probably
needs some more discussion, not worth blocking this patch for that.

For pr_warn and friends, one approach is defining pr_fmt() macro at the
top.


BR,
Jani.




>
> Best regards,
>
> Lukas
>
>>  		mode->specified = false;
>>  		return false;
>> -- 
>> 2.4.10
>> 
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
> _______________________________________________
> dri-devel mailing list
> dri-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Jani Nikula, Intel Open Source Technology Center


More information about the dri-devel mailing list