AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Das, Nirmoy" <nirmoy.das@intel.com>,
	Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel@lists.freedesktop.org, Sam Ravnborg <sam@ravnborg.org>,
	amd-gfx@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH 2/2] drm_print: Remove deprecated DRM_DEBUG_KMS_RATELIMITED()
Date: Wed, 18 Jan 2023 07:27:29 +0100	[thread overview]
Message-ID: <bf60d3dc-1d6b-4f74-79f2-878cd61ba3bd@gmail.com> (raw)
In-Reply-To: <982599d1-2480-72ff-1515-425b2693e3b5@intel.com>



Am 17.01.23 um 19:12 schrieb Das, Nirmoy:
> Hi Alex,
>
> On 1/17/2023 7:06 PM, Alex Deucher wrote:
>> On Tue, Jan 17, 2023 at 1:05 PM Nirmoy Das <nirmoy.das@intel.com> wrote:
>>> There are no current users of DRM_DEBUG_KMS_RATELIMITED()
>>> so remove it.
>>>
>>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>>> Cc: Maxime Ripard <mripard@kernel.org>
>>> Cc: Thomas Zimmermann <tzimmermann@suse.de>
>>> Cc: David Airlie <airlied@gmail.com>
>>> Cc: Daniel Vetter <daniel@ffwll.ch>
>>> Cc: Sam Ravnborg <sam@ravnborg.org>
>>>
>>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>>> Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
>> Series is:
>> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
>>
>> Feel free to take the patches through whatever tree you want.
>
>
> Please help me with this, I don't have committer rights for any tree.

Going to push that into drm-misc-next later today.

Thanks,
Christian.

>
>
> Nirmoy
>
>
>>
>> Alex
>>
>>> ---
>>>   include/drm/drm_print.h | 3 ---
>>>   1 file changed, 3 deletions(-)
>>>
>>> diff --git a/include/drm/drm_print.h b/include/drm/drm_print.h
>>> index a44fb7ef257f..c3753da97c4e 100644
>>> --- a/include/drm/drm_print.h
>>> +++ b/include/drm/drm_print.h
>>> @@ -605,9 +605,6 @@ void __drm_err(const char *format, ...);
>>>   #define drm_dbg_kms_ratelimited(drm, fmt, ...) \
>>>          __DRM_DEFINE_DBG_RATELIMITED(KMS, drm, fmt, ## __VA_ARGS__)
>>>
>>> -/* NOTE: this is deprecated in favor of 
>>> drm_dbg_kms_ratelimited(NULL, ...). */
>>> -#define DRM_DEBUG_KMS_RATELIMITED(fmt, ...) 
>>> drm_dbg_kms_ratelimited(NULL, fmt, ## __VA_ARGS__)
>>> -
>>>   /*
>>>    * struct drm_device based WARNs
>>>    *
>>> -- 
>>> 2.39.0
>>>


  reply	other threads:[~2023-01-18  6:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 18:04 [PATCH v2] drm/radeon: Do not use deprecated drm log API Nirmoy Das
2023-01-17 18:04 ` [PATCH 2/2] drm_print: Remove deprecated DRM_DEBUG_KMS_RATELIMITED() Nirmoy Das
2023-01-17 18:06   ` Alex Deucher
2023-01-17 18:12     ` Das, Nirmoy
2023-01-18  6:27       ` Christian König [this message]
2023-01-18  9:34         ` Das, Nirmoy
2023-01-19  7:56 ` [PATCH v2] drm/radeon: Do not use deprecated drm log API Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2023-01-17 17:44 [PATCH 1/2] " Nirmoy Das
2023-01-17 17:44 ` [PATCH 2/2] drm_print: Remove deprecated DRM_DEBUG_KMS_RATELIMITED() Nirmoy Das
2023-01-17 17:59   ` 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=bf60d3dc-1d6b-4f74-79f2-878cd61ba3bd@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=nirmoy.das@intel.com \
    --cc=sam@ravnborg.org \
    --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