From: Eric Engestrom <eric.engestrom@imgtec.com>
To: Sean Paul <seanpaul@chromium.org>
Cc: linux-rockchip@lists.infradead.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 1/2] drm: Introduce DRM_DEV_* log messages
Date: Mon, 15 Aug 2016 13:54:52 +0100 [thread overview]
Message-ID: <20160815125452.GB10429@imgtec.com> (raw)
In-Reply-To: <1471033777-9922-1-git-send-email-seanpaul@chromium.org>
On Fri, Aug 12, 2016 at 04:29:37PM -0400, Sean Paul wrote:
> This patch consolidates all the various log functions/macros into
> one uber function, drm_printk. It also introduces some new DRM_DEV_*
> variants that use dev_printk to print the device name, which helps
> delineate multiple devices of the same type.
>
> Signed-off-by: Sean Paul <seanpaul@chromium.org>
> ---
>
> Changes in v2:
> - Use dev_printk for the dev variant (Chris Wilson)
>
> Changes in v3:
> - Rename drm_log to drm_dev_printk (Chris Wilson)
> - Break out drm_printk from drm_dev_printk to reduce
> image growth due to passing NULL around (Chris Wilson)
>
> drivers/gpu/drm/drm_drv.c | 25 ++++++---
> include/drm/drmP.h | 140 +++++++++++++++++++++++++++-------------------
> 2 files changed, 101 insertions(+), 64 deletions(-)
>
[snip]
> + dev_printk(level, dev, "[" DRM_NAME ":%s]%s %pV", function_name, prefix,
> + &vaf);
[...]
> + printk("%s[" DRM_NAME ":%s]%s %pV", level, function_name, prefix, &vaf);
What do you think of #define'ing them to make sure these two format strings
don't end up diverging at some point?
Cheers,
Eric
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-15 12:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 17:00 [PATCH 0/2] Introduce DRM_DEV_* logging Sean Paul
2016-08-12 17:00 ` [PATCH 1/2] drm: Introduce DRM_DEV_* log messages Sean Paul
[not found] ` <1471021254-2563-2-git-send-email-seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-08-12 17:13 ` Chris Wilson
2016-08-12 17:23 ` Sean Paul
2016-08-12 17:30 ` [PATCH v2 " Sean Paul
[not found] ` <1471023000-3820-1-git-send-email-seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-08-12 18:39 ` Chris Wilson
2016-08-12 19:04 ` Sean Paul
2016-08-12 19:26 ` Lukas Wunner
2016-08-12 19:44 ` Chris Wilson
2016-08-12 19:48 ` Sean Paul
2016-08-12 19:50 ` Lukas Wunner
2016-08-12 20:29 ` [PATCH v3 " Sean Paul
[not found] ` <1471033777-9922-1-git-send-email-seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-08-12 20:53 ` Chris Wilson
2016-08-15 12:54 ` Eric Engestrom [this message]
2016-08-15 23:18 ` [PATCH v4] " Sean Paul
2016-08-16 12:28 ` Eric Engestrom
2016-08-16 16:18 ` Sean Paul
2016-08-16 16:56 ` Eric Engestrom
2016-08-18 16:39 ` Sean Paul
2016-08-12 17:00 ` [PATCH 2/2] drm/rockchip: Use DRM_DEV_ERROR in vop Sean Paul
2016-08-18 8:53 ` Mark yao
2016-08-18 16:38 ` Sean Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160815125452.GB10429@imgtec.com \
--to=eric.engestrom@imgtec.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=seanpaul@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.