dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Karol Wachowski <karol.wachowski@linux.intel.com>,
	dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jeff.hugo@oss.qualcomm.com,
	maciej.falkowski@linux.intel.com, lizhi.hou@amd.com
Subject: Re: [PATCH v2] accel/ivpu: Improve debug and warning messages
Date: Tue, 04 Nov 2025 16:39:47 +0200	[thread overview]
Message-ID: <d8cdb0c5c420b7ac9bf64367a25d2ad6dff95637@intel.com> (raw)
In-Reply-To: <cefbd464-2f0f-4055-ab6e-9b76047794b2@linux.intel.com>

On Tue, 04 Nov 2025, Karol Wachowski <karol.wachowski@linux.intel.com> wrote:
> On 11/4/2025 2:00 PM, Jani Nikula wrote:
>> On Tue, 04 Nov 2025, Karol Wachowski <karol.wachowski@linux.intel.com> wrote:
>>>  #define ivpu_warn_ratelimited(vdev, fmt, ...) \
>>> -	drm_err_ratelimited(&(vdev)->drm, "%s(): " fmt, __func__, ##__VA_ARGS__)
>>> +	__drm_printk(&(vdev)->drm, warn, _ratelimited, fmt, ##__VA_ARGS__)
>> The double underscore is a hint that it's private, don't use it outside
>> of drm_print.h.
>>
>> BR,
>> Jani.
>
> Thanks, I will remove this. BTW is there a reason for
> drm_warn_ratelimited not existing in drm_print.h?

I can't think of a reason other than not having a user and not wanting
to pre-emptively add a bunch of macros that aren't used.

BR,
Jani.


-- 
Jani Nikula, Intel

      reply	other threads:[~2025-11-04 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04  9:00 [PATCH v2] accel/ivpu: Improve debug and warning messages Karol Wachowski
2025-11-04 13:00 ` Jani Nikula
2025-11-04 13:16   ` Karol Wachowski
2025-11-04 14:39     ` Jani Nikula [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=d8cdb0c5c420b7ac9bf64367a25d2ad6dff95637@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=karol.wachowski@linux.intel.com \
    --cc=lizhi.hou@amd.com \
    --cc=maciej.falkowski@linux.intel.com \
    --cc=oded.gabbay@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