From: John Harrison <john.c.harrison@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: Daniel Vetter <daniel@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Maxime Ripard <mripard@kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Nirmoy Das <nirmoy.das@intel.com>,
David Airlie <airlied@gmail.com>,
Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/print: Add drm_dbg_ratelimited
Date: Mon, 9 Oct 2023 12:52:48 -0700 [thread overview]
Message-ID: <9a54284d-406e-4d7a-b39b-293d2e449961@intel.com> (raw)
In-Reply-To: <ZSRX+0BB3Mf5diMC@ashyti-mobl2.lan>
On 10/9/2023 12:43, Andi Shyti wrote:
> Hi John,
>
>>>> From: Nirmoy Das <nirmoy.das@intel.com>
>>>>
>>>> Add a function for ratelimitted debug print.
>>>>
>>>> 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>
>>>> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>>>> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
>>>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>>>> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
>>> Just a kind reminder!
>>>
>>> This is the second time this patch has been sent and we have seen
>>> some potential use of the drm_dbg_ratelimited().
>> But this patch does not actually add a user. So it is dead code at this
>> point, which is not allowed.
>>
>> If you have code that wants to use such a helper then the helper should be
>> part of the patch that adds that code.
> this is the kind of "Argh! If I had it!" patch. At the 3/4th
> "Argh! If I had it!" then you decide to send it but don't
> remember for which case you needed it.
But you should have sent it on the 1st patch set that wanted it.
And if you have code already merged that would benefit from it, then
update that code to use it and post that as a patch together with this
implementation.
And note that if your code is GT related, then it should use
gt_dbg_ratelimited not drm_dbg_ratelimited.
John.
>
> I'm sure that once this goes in won't be long until poeple will
> start using it. In any case, if it doesn't go in I will keep it
> ready until the case comes.
>
> Andi
prev parent reply other threads:[~2023-10-09 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 13:26 [Intel-gfx] [PATCH] drm/print: Add drm_dbg_ratelimited Andi Shyti
2023-10-06 16:44 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-10-06 16:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-07 5:43 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-10-09 16:52 ` [Intel-gfx] [PATCH] " Andi Shyti
2023-10-09 18:52 ` John Harrison
2023-10-09 19:43 ` Andi Shyti
2023-10-09 19:52 ` John Harrison [this message]
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=9a54284d-406e-4d7a-b39b-293d2e449961@intel.com \
--to=john.c.harrison@intel.com \
--cc=airlied@gmail.com \
--cc=andi.shyti@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=mripard@kernel.org \
--cc=nirmoy.das@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