From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] drm: add DRM_DEBUG_CORE() and friends and use them
Date: Thu, 10 Jan 2019 17:27:10 +0200 [thread overview]
Message-ID: <877efc7ctt.fsf@intel.com> (raw)
In-Reply-To: <20181227162310.13023-1-jani.nikula@intel.com>
On Thu, 27 Dec 2018, Jani Nikula <jani.nikula@intel.com> wrote:
> DRM_DEBUG() was intended to be used by the drm core code only, but we
> weren't careful. Today, the driver usage of DRM_DEBUG() trumps drm core
> usage about 10:1. It's easier to swith the core over to a new
> DRM_DEBUG_CORE() macro than the drivers over to DRM_DEBUG_DRIVER().
>
> Do the same for DRM_DEV_DEBUG() and the ratelimited ones as well.
Any thoughts on this one? Or should we just decide we don't need to
distinguish between core and drivers? Or should we move towards dev
based logging altogether?
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-01-10 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 16:23 [RFC] drm: add DRM_DEBUG_CORE() and friends and use them Jani Nikula
2018-12-27 16:46 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-12-27 16:48 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-27 17:04 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-27 19:46 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-10 15:27 ` Jani Nikula [this message]
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=877efc7ctt.fsf@intel.com \
--to=jani.nikula@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 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.