From: Joe Perches <joe@perches.com>
To: Lyude Paul <lyude@redhat.com>, nouveau@lists.freedesktop.org
Cc: Karol Herbst <kherbst@redhat.com>,
Ben Skeggs <bskeggs@redhat.com>, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/6] drm/nouveau: Add NV_PRINTK_ONCE and variants
Date: Thu, 06 Sep 2018 22:35:59 -0700 [thread overview]
Message-ID: <4d74256435a71cdb7ec8d114b1c3cb640f29c267.camel@perches.com> (raw)
In-Reply-To: <20180906214328.24012-3-lyude@redhat.com>
On Thu, 2018-09-06 at 17:43 -0400, Lyude Paul wrote:
> Since we're about to use this in nouveau_backlight.c. Same thing as
> DRM_WARN_ONCE, DRM_INFO_ONCE, etc...
Can you redefine this in terms of the patches I submitted
instead?
https://lore.kernel.org/patchwork/patch/979598/
https://lore.kernel.org/patchwork/patch/979601/
> Signed-off-by: Lyude Paul <lyude@redhat.com>
> Cc: Karol Herbst <kherbst@redhat.com>
> ---
> drivers/gpu/drm/nouveau/nouveau_drv.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/nouveau/nouveau_drv.h b/drivers/gpu/drm/nouveau/nouveau_drv.h
> index 6e1acaec3400..d9d687916553 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_drv.h
> +++ b/drivers/gpu/drm/nouveau/nouveau_drv.h
> @@ -244,10 +244,12 @@ void nouveau_drm_device_remove(struct drm_device *dev);
> struct nouveau_cli *_cli = (c); \
> dev_##l(_cli->drm->dev->dev, "%s: "f, _cli->name, ##a); \
> } while(0)
> +
> #define NV_FATAL(drm,f,a...) NV_PRINTK(crit, &(drm)->client, f, ##a)
> #define NV_ERROR(drm,f,a...) NV_PRINTK(err, &(drm)->client, f, ##a)
> #define NV_WARN(drm,f,a...) NV_PRINTK(warn, &(drm)->client, f, ##a)
> #define NV_INFO(drm,f,a...) NV_PRINTK(info, &(drm)->client, f, ##a)
> +
> #define NV_DEBUG(drm,f,a...) do { \
> if (unlikely(drm_debug & DRM_UT_DRIVER)) \
> NV_PRINTK(info, &(drm)->client, f, ##a); \
> @@ -257,6 +259,12 @@ void nouveau_drm_device_remove(struct drm_device *dev);
> NV_PRINTK(info, &(drm)->client, f, ##a); \
> } while(0)
>
> +#define NV_PRINTK_ONCE(l,c,f,a...) NV_PRINTK(l##_once,c,f, ##a)
> +
> +#define NV_ERROR_ONCE(drm,f,a...) NV_PRINTK_ONCE(err, &(drm)->client, f, ##a)
> +#define NV_WARN_ONCE(drm,f,a...) NV_PRINTK_ONCE(warn, &(drm)->client, f, ##a)
> +#define NV_INFO_ONCE(drm,f,a...) NV_PRINTK_ONCE(info, &(drm)->client, f, ##a)
> +
> extern int nouveau_modeset;
>
> #endif
next prev parent reply other threads:[~2018-09-07 5:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 21:43 [PATCH v4 0/6] Backlight fixes and cleanup Lyude Paul
2018-09-06 21:43 ` [PATCH v4 1/6] drm/nouveau: Check backlight IDs are >= 0, not > 0 Lyude Paul
2018-09-06 21:43 ` [PATCH v4 2/6] drm/nouveau: Add NV_PRINTK_ONCE and variants Lyude Paul
2018-09-07 5:35 ` Joe Perches [this message]
2018-09-07 17:27 ` Lyude Paul
2018-09-06 21:43 ` [PATCH v4 3/6] drm/nouveau: Move backlight device into nouveau_connector Lyude Paul
2018-09-06 21:43 ` [PATCH v4 4/6] drm/nouveau: s/nouveau_backlight_exit/nouveau_backlight_fini/ Lyude Paul
2018-09-06 21:43 ` [PATCH v4 5/6] drm/nouveau: Cleanup indenting in nouveau_backlight.c Lyude Paul
2018-09-06 21:43 ` [PATCH v4 6/6] drm/nouveau: Refactor nvXX_backlight_init() Lyude 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=4d74256435a71cdb7ec8d114b1c3cb640f29c267.camel@perches.com \
--to=joe@perches.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@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
Powered by JetHome