dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Wachowski, Karol" <karol.wachowski@linux.intel.com>
To: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>,
	dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jeff.hugo@oss.qualcomm.com,
	lizhi.hou@amd.com, andrzej.kacprowski@linux.intel.com
Subject: Re: [PATCH RESEND 0/2] drm: add drm_warn_ratelimited() and convert ivpu to use it
Date: Mon, 24 Aug 2026 10:11:24 +0200	[thread overview]
Message-ID: <7813eba9-cea7-4c00-9062-0d4b961792a6@linux.intel.com> (raw)
In-Reply-To: <20260820104811.803146-1-dawid.osuchowski@linux.intel.com>

On 20-Aug-26 12:48, Dawid Osuchowski wrote:
> This patch set adds drm_warn_ratelimited() to the DRM print helpers
> and updates the ivpu driver to use the warning-level variant instead
> of err-level logging. The new helper matches the existing rate-limited
> logging pattern and gives drivers a consistent way to emit warning
> messages without spamming the kernel log.
> 
> This change improves logging correctness and consistency for drivers
> that need rate-limited warnings.
> 
> 
> Dawid Osuchowski (2):
>    drm/print: add drm_warn_ratelimited logging macro
>    accel/ivpu: Use drm_warn_ratelimited macro
> 
>   drivers/accel/ivpu/ivpu_drv.h | 2 +-
>   include/drm/drm_print.h       | 3 +++
>   2 files changed, 4 insertions(+), 1 deletion(-)
> 
> 
> base-commit: 063019ac51afffda4ab3d658701b086caa0c8e9e

Thanks.
Applied to drm-misc-next.

      parent reply	other threads:[~2026-08-24  8:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 10:48 [PATCH RESEND 0/2] drm: add drm_warn_ratelimited() and convert ivpu to use it Dawid Osuchowski
2026-08-20 10:48 ` [PATCH RESEND 1/2] drm/print: add drm_warn_ratelimited logging macro Dawid Osuchowski
2026-08-20 10:57   ` Wachowski, Karol
2026-08-20 10:48 ` [PATCH RESEND 2/2] accel/ivpu: Use drm_warn_ratelimited macro Dawid Osuchowski
2026-08-20 10:57   ` Wachowski, Karol
2026-08-24  8:11 ` Wachowski, Karol [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=7813eba9-cea7-4c00-9062-0d4b961792a6@linux.intel.com \
    --to=karol.wachowski@linux.intel.com \
    --cc=andrzej.kacprowski@linux.intel.com \
    --cc=dawid.osuchowski@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=lizhi.hou@amd.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