From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Sean Paul <sean@poorly.run>,
DRI Development <dri-devel@lists.freedesktop.org>,
Wambui Karuga <wambui.karugax@gmail.com>
Subject: Re: [PATCH] drm/todo: Updating logging todo
Date: Thu, 19 Dec 2019 22:14:04 +0100 [thread overview]
Message-ID: <20191219211404.GF624164@phenom.ffwll.local> (raw)
In-Reply-To: <87r210wabi.fsf@intel.com>
On Thu, Dec 19, 2019 at 06:26:41PM +0200, Jani Nikula wrote:
> On Thu, 19 Dec 2019, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > Jani has merged a new set of logging functions, which we hope to be
> > the One True solution now, pinky promises:
> >
> > commit fb6c7ab8718eb2543695d77ad8302ff81e8e1e32
> > Author: Jani Nikula <jani.nikula@intel.com>
> > Date: Tue Dec 10 14:30:43 2019 +0200
> >
> > drm/print: introduce new struct drm_device based logging macros
> >
> > Update the todo entry to match the new preference.
> >
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Cc: Sean Paul <sean@poorly.run>
> > Cc: Wambui Karuga <wambui.karugax@gmail.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
>
> Might mention converting everything to the One True solution, but
> *shrug*.
>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
Patch applied. And thanks for wrangling this bikeshed into at least a less
yelling color :-)
Cheers, Daniel
>
> > ---
> > Documentation/gpu/todo.rst | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
> > index 2d85f37284a1..017f3090f8a1 100644
> > --- a/Documentation/gpu/todo.rst
> > +++ b/Documentation/gpu/todo.rst
> > @@ -142,13 +142,13 @@ Contact: Daniel Vetter, respective driver maintainers
> >
> > Level: Advanced
> >
> > -Convert instances of dev_info/dev_err/dev_warn to their DRM_DEV_* equivalent
> > -----------------------------------------------------------------------------
> > +Convert logging to drm_* functions with drm_device paramater
> > +------------------------------------------------------------
> >
> > For drivers which could have multiple instances, it is necessary to
> > differentiate between which is which in the logs. Since DRM_INFO/WARN/ERROR
> > don't do this, drivers used dev_info/warn/err to make this differentiation. We
> > -now have DRM_DEV_* variants of the drm print macros, so we can start to convert
> > +now have drm_* variants of the drm print functions, so we can start to convert
> > those drivers back to using drm-formwatted specific log messages.
> >
> > Before you start this conversion please contact the relevant maintainers to make
>
> --
> Jani Nikula, Intel Open Source Graphics Center
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-12-19 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 16:17 [PATCH] drm/todo: Updating logging todo Daniel Vetter
2019-12-19 16:26 ` Jani Nikula
2019-12-19 21:14 ` Daniel Vetter [this message]
2019-12-19 16:53 ` Sam Ravnborg
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=20191219211404.GF624164@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=sean@poorly.run \
--cc=wambui.karugax@gmail.com \
/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.