mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Siddh Raman Pant <code@siddh.me>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Andrzej Hajda <andrzej.hajda@intel.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Robert Foss <rfoss@kernel.org>, Jonas Karlman <jonas@kwiboo.se>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Suraj Upadhyay <usuraj35@gmail.com>
Subject: Re: [PATCH v9 0/8] drm: Remove usage of deprecated DRM_* macros
Date: Tue, 6 Jun 2023 20:49:28 +0300	[thread overview]
Message-ID: <20230606174928.GB14101@pendragon.ideasonboard.com> (raw)
In-Reply-To: <18891c17458.393a54b1127185.1502341592143085000@siddh.me>

On Tue, Jun 06, 2023 at 10:59:14PM +0530, Siddh Raman Pant wrote:
> On Tue, 06 Jun 2023 20:35:45 +0530, Laurent Pinchart wrote:
> > This is a nice series, thank you for working on that.
> > 
> > Now that the deprecated macros are used in drivers only, would it make
> > sense to move them to a drm_print_deprecated.h header, to make sure no
> > new driver uses them ?
> 
> Sure, but then should that header be included wherever drm_print.h is
> included with a find and replace, to avoid breakage?

The idea would be to include the drm_print_deprecated.h header in
drivers that still use the deprecated macros.

> Not every file can be seen at a case-by-case basis or by coccinelle
> as far as I understand its usage. Consider the following:
> 
> DRM_INFO is used on line 210 of amd/amdgpu/amdgpu_acpi.c, but the
> file does not even include drm_print.h directly. It includes the
> amdgpu.h header, which includes the amdgpu_ring.h header, which
> finally has the "#include <drm/drm_print.h>" line.
> 
> If a simple find and replace has to be done, then that can be added
> at the end of the series.

Maybe a simple grep for the deprecated macros would be enough to
identify all the files that still use them ?

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2023-06-06 17:49 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 10:45 Siddh Raman Pant
2023-06-06 10:45 ` [PATCH v9 1/8] Revert "drm: mipi-dsi: Convert logging to drm_* functions." Siddh Raman Pant
2023-06-06 12:55   ` Laurent Pinchart
2023-06-06 13:07     ` Jani Nikula
2023-06-06 13:21     ` Siddh Raman Pant
2023-06-06 10:45 ` [PATCH v9 2/8] drm/print: Fix and add support for NULL as first argument in drm_* macros Siddh Raman Pant
2023-06-06 14:05   ` Laurent Pinchart
2023-06-06 14:34     ` Siddh Raman Pant
2023-06-06 14:47       ` Laurent Pinchart
2023-06-06 10:45 ` [PATCH v9 3/8] drm: Remove usage of deprecated DRM_INFO Siddh Raman Pant
2023-06-06 14:23   ` Laurent Pinchart
2023-06-06 14:38     ` Siddh Raman Pant
2023-06-06 14:46       ` Laurent Pinchart
2023-06-06 16:39         ` Siddh Raman Pant
2023-06-06 10:45 ` [PATCH v9 4/8] drm: Remove usage of deprecated DRM_NOTE Siddh Raman Pant
2023-06-06 14:39   ` Laurent Pinchart
2023-06-06 10:45 ` [PATCH v9 5/8] drm: Remove usage of deprecated DRM_ERROR Siddh Raman Pant
2023-06-06 14:44   ` Laurent Pinchart
2023-06-06 17:06     ` Siddh Raman Pant
2023-06-06 17:13       ` Laurent Pinchart
2023-06-06 10:45 ` [PATCH v9 6/8] drm: Remove usage of deprecated DRM_DEBUG Siddh Raman Pant
2023-06-06 14:57   ` Laurent Pinchart
2023-06-06 17:14     ` Siddh Raman Pant
2023-06-06 10:45 ` [PATCH v9 7/8] drm: Remove usage of deprecated DRM_DEBUG_DRIVER Siddh Raman Pant
2023-06-06 14:38   ` Laurent Pinchart
2023-06-06 10:45 ` [PATCH v9 8/8] drm: Remove usage of deprecated DRM_DEBUG_KMS Siddh Raman Pant
2023-06-06 15:04   ` Laurent Pinchart
2023-06-06 17:17     ` Siddh Raman Pant
2023-06-06 21:39     ` Jani Nikula
2023-06-07  3:53       ` Laurent Pinchart
2023-06-07  8:12         ` Jani Nikula
2023-06-06 11:30 ` [PATCH v9 0/8] drm: Remove usage of deprecated DRM_* macros Jani Nikula
2023-06-06 15:05 ` Laurent Pinchart
2023-06-06 17:29   ` Siddh Raman Pant
2023-06-06 17:49     ` Laurent Pinchart [this message]
2023-06-06 18:17       ` Siddh Raman Pant
2023-06-07  4:30         ` Laurent Pinchart

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=20230606174928.GB14101@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=code@siddh.me \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=tzimmermann@suse.de \
    --cc=usuraj35@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®