Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1738790 > unrolled thread

Re: [PATCH v2] drm/tegra: Replace dev_* with DRM_DEV_*

Started byThierry Reding <thierry.reding@gmail.com>
First post2017-09-25 09:40 +0200
Last post2017-09-25 09:40 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v2] drm/tegra: Replace dev_* with DRM_DEV_* Thierry Reding <thierry.reding@gmail.com> - 2017-09-25 09:40 +0200

#1738790 — Re: [PATCH v2] drm/tegra: Replace dev_* with DRM_DEV_*

FromThierry Reding <thierry.reding@gmail.com>
Date2017-09-25 09:40 +0200
SubjectRe: [PATCH v2] drm/tegra: Replace dev_* with DRM_DEV_*
Message-ID<utw9H-3eX-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

On Sun, Sep 24, 2017 at 10:13:57PM +0530, Harsha Sharma wrote:
> Replace all occurences of dev_info/err/dbg with DRM_DEV_INFO/
> ERROR/DEBUG as we have DRM_DEV_* variants of drm print macros
> Done using following coccinelle semantic patch
> 
> @r@
> @@
> 
> (
> -dev_info
> +DRM_DEV_INFO
> |
> -dev_err
> +DRM_DEV_ERROR
> |
> -dev_dbg
> +DRM_DEV_DEBUG
> )
> 
> Signed-off-by: Harsha Sharma <harshasharmaiitr@gmail.com>
> ---
> Changes in v2:
>  -Break line over 80 characters
>  -Changes in comments not required

Please don't do this. Most of the functions that you're trying to
replace here are not DRM_DEV_*() for a very specific reason: none of
them have anything to do with DRM/KMS in particular. This is important,
in my opinion, because these messages are very device-specific and the
additional information added by the DRM format string aren't useful in
the context.

Perhaps the only ones I consider to be good candidates for this
conversion are the ones in drivers/gpu/drm/tegra/fb.c because they deal
with the DRM fbdev setup and hence are not device specific. And even in
those cases I'm not sure we gain very much by this conversion,
especially since most of the replacements now end up having to split up
argument lists.

Sorry if this isn't documented anywhere. I also suspect other driver
maintainers will be less picky about this sort of thing, so you might
have more luck there.

Thierry

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web