From: Sam Ravnborg <sam@ravnborg.org>
To: Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@intel.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
Jonathan Corbet <corbet@lwn.net>, David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/todo: Add todo to make i915 WARN* calls drm device specific
Date: Mon, 30 Mar 2020 21:27:23 +0200 [thread overview]
Message-ID: <20200330192723.GA22772@ravnborg.org> (raw)
In-Reply-To: <20200330191524.14676-1-pankaj.laxminarayan.bharadiya@intel.com>
Hi Pankaj.
On Tue, Mar 31, 2020 at 12:45:24AM +0530, Pankaj Bharadiya wrote:
> With below commit, we have new struct drm_device based WARN* macros,
> which include device specific information in the backtrace.
>
> commit dc1a73e50f9c63d4dd928df538082200467dc4b1
> Author: Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@intel.com>
> Date: Wed Jan 15 09:14:45 2020 +0530
>
> drm/print: introduce new struct drm_device based WARN* macros
>
> Majority of the i915 WARN* are already converted to use struct
> drm_device specific drm_WARN* calls.Add new todo entry for
Add space after '.'
> pending conversions.
>
> Signed-off-by: Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@intel.com>
> ---
> Documentation/gpu/todo.rst | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
> index 37a3a023c114..0cb32df89784 100644
> --- a/Documentation/gpu/todo.rst
> +++ b/Documentation/gpu/todo.rst
> @@ -575,6 +575,18 @@ See drivers/gpu/drm/amd/display/TODO for tasks.
>
> Contact: Harry Wentland, Alex Deucher
>
> +Make i915 WARN* Calls struct drm_device Specific
> +------------------------------------------------
> +
> +struct drm_device specific drm_WARN* macros include device information in the
> +backtrace, so we know what device the warnings originate from. Convert all the
> +calls of WARN* with drm_WARN* calls in i915. While at it, remove WARN* which
> +are not truly valid.
> +
> +Contact: Jani Nikula
> +
> +Level: Starter
> +
> Bootsplash
> ==========
>
> @@ -595,7 +607,7 @@ Level: Advanced
> Outside DRM
> ===========
>
> -Convert fbdev drivers to DRM
> +Convert fbdev drivers to
Unrelated change?
Please fix and re-submit.
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-03-30 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 19:15 [PATCH] drm/todo: Add todo to make i915 WARN* calls drm device specific Pankaj Bharadiya
2020-03-30 19:27 ` Sam Ravnborg [this message]
2020-03-30 19:29 ` Laxminarayan Bharadiya, Pankaj
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=20200330192723.GA22772@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pankaj.laxminarayan.bharadiya@intel.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).