From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jeff.hugo@oss.qualcomm.com,
karol.wachowski@linux.intel.com, lizhi.hou@amd.com,
andrzej.kacprowski@linux.intel.com,
Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Subject: [PATCH RESEND 2/2] accel/ivpu: Use drm_warn_ratelimited macro
Date: Thu, 20 Aug 2026 12:48:11 +0200 [thread overview]
Message-ID: <20260820104811.803146-3-dawid.osuchowski@linux.intel.com> (raw)
In-Reply-To: <20260820104811.803146-1-dawid.osuchowski@linux.intel.com>
Fix ivpu_warn_ratelimited() to properly use WARN logging level instead
of an ERROR.
Signed-off-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
---
drivers/accel/ivpu/ivpu_drv.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/accel/ivpu/ivpu_drv.h b/drivers/accel/ivpu/ivpu_drv.h
index 86d7c9966cac..8f29f1dc52b9 100644
--- a/drivers/accel/ivpu/ivpu_drv.h
+++ b/drivers/accel/ivpu/ivpu_drv.h
@@ -91,7 +91,7 @@
drm_warn(&(vdev)->drm, "%s(): " fmt, __func__, ##__VA_ARGS__)
#define ivpu_warn_ratelimited(vdev, fmt, ...) \
- drm_err_ratelimited(&(vdev)->drm, "%s(): " fmt, __func__, ##__VA_ARGS__)
+ drm_warn_ratelimited(&(vdev)->drm, "%s(): " fmt, __func__, ##__VA_ARGS__)
#define ivpu_info(vdev, fmt, ...) drm_info(&(vdev)->drm, fmt, ##__VA_ARGS__)
--
2.43.0
next prev parent reply other threads:[~2026-08-20 10:53 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 ` Dawid Osuchowski [this message]
2026-08-20 10:57 ` [PATCH RESEND 2/2] accel/ivpu: Use drm_warn_ratelimited macro Wachowski, Karol
2026-08-24 8:11 ` [PATCH RESEND 0/2] drm: add drm_warn_ratelimited() and convert ivpu to use it Wachowski, Karol
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=20260820104811.803146-3-dawid.osuchowski@linux.intel.com \
--to=dawid.osuchowski@linux.intel.com \
--cc=andrzej.kacprowski@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=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