From: Eric Engestrom <eric.engestrom@imgtec.com>
To: Dave Gordon <david.s.gordon@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v5 1/4] drm: two more (drm_)printk() wrapper macros
Date: Tue, 30 Aug 2016 10:43:51 +0100 [thread overview]
Message-ID: <20160830094351.GR24583@imgtec.com> (raw)
In-Reply-To: <1472233859-31837-2-git-send-email-david.s.gordon@intel.com>
On Fri, Aug 26, 2016 at 06:50:56PM +0100, Dave Gordon wrote:
> We had only DRM_INFO() and DRM_ERROR(), whereas the underlying printk()
> provides several other useful intermediate levels such as NOTICE and
> WARNING. So this patch fills out the set by providing simple macros for
> the additional levels. We don't provide _DEV_ or _ONCE or RATELIMITED
> versions yet as it seems unlikely that they'll be as useful.
>
> v2:
> Fix whitespace, missing ## (Eric Engestrom)
> v5:
> Much simplified after underlying functions were reworked.
>
> Signed-off-by: Dave Gordon <david.s.gordon@intel.com>
> Previously-Reviewed-by: Eric Engestrom <eric.engestrom@imgtec.com> (v2)
My r-b still stands on the v5 (and I really like the simplification!)
Thanks for CC'ing me on the updates :)
Cheers,
Eric
> Cc: Eric Engestrom <eric.engestrom@imgtec.com>
> Cc: dri-devel@lists.freedesktop.org
> ---
> include/drm/drmP.h | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/include/drm/drmP.h b/include/drm/drmP.h
> index 94eb138..cd52624 100644
> --- a/include/drm/drmP.h
> +++ b/include/drm/drmP.h
> @@ -168,6 +168,13 @@ void drm_printk(const char *level, unsigned int category,
> /** \name Macros to make printk easier */
> /*@{*/
>
> +#define DRM_INFO(fmt, ...) \
> + drm_printk(KERN_INFO, DRM_UT_NONE, __func__, "", fmt, ##__VA_ARGS__)
> +#define DRM_NOTE(fmt, ...) \
> + drm_printk(KERN_NOTICE, DRM_UT_NONE, __func__, "", fmt, ##__VA_ARGS__)
> +#define DRM_WARN(fmt, ...) \
> + drm_printk(KERN_WARNING, DRM_UT_NONE, __func__, "", fmt, ##__VA_ARGS__)
> +
> /**
> * Error output.
> *
> @@ -202,8 +209,6 @@ void drm_printk(const char *level, unsigned int category,
> #define DRM_DEV_INFO(dev, fmt, ...) \
> drm_dev_printk(dev, KERN_INFO, DRM_UT_NONE, __func__, "", fmt, \
> ##__VA_ARGS__)
> -#define DRM_INFO(fmt, ...) \
> - drm_printk(KERN_INFO, DRM_UT_NONE, __func__, "", fmt, ##__VA_ARGS__)
>
> #define DRM_DEV_INFO_ONCE(dev, fmt, ...) \
> ({ \
> --
> 1.9.1
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-30 9:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 17:50 [PATCH v5 0/4] Reclassify messages from GuC loader/submission Dave Gordon
2016-08-26 17:50 ` [PATCH v5 1/4] drm: two more (drm_)printk() wrapper macros Dave Gordon
2016-08-26 18:00 ` Chris Wilson
2016-08-30 9:43 ` Eric Engestrom [this message]
2016-09-06 13:34 ` Sean Paul
2016-08-26 17:50 ` [PATCH v5 2/4] drm/i915/guc: downgrade some DRM_ERROR() messages to DRM_WARN() Dave Gordon
2016-08-26 17:50 ` [PATCH v5 3/4] drm/i915/guc: revisit GuC loader message levels Dave Gordon
2016-08-26 17:50 ` [PATCH v5 4/4] NOMERGE: next version of GuC firmware is 8.11 Dave Gordon
2016-08-26 18:50 ` ✗ Fi.CI.BAT: warning for Reclassify messages from GuC loader/submission (rev5) Patchwork
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=20160830094351.GR24583@imgtec.com \
--to=eric.engestrom@imgtec.com \
--cc=david.s.gordon@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox