From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: alex.zuo@intel.com, jonathan.cavitt@intel.com,
michal.wajdeczko@intel.com, raag.jadav@intel.com,
andi.shyti@linux.intel.com, jani.nikula@intel.com
Subject: [PATCH v6 1/3] drm/xe/printk: Add xe_warn_once()
Date: Thu, 3 Sep 2026 03:58:49 +0800 [thread overview]
Message-ID: <20260902195851.306669-2-jonathan.cavitt@intel.com> (raw)
In-Reply-To: <20260902195851.306669-1-jonathan.cavitt@intel.com>
Create a wrapper function xe_warn_once() that calls drm_warn_once().
Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
drivers/gpu/drm/xe/xe_printk.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_printk.h b/drivers/gpu/drm/xe/xe_printk.h
index 87f51d7edfa8b..79db1f78e822c 100644
--- a/drivers/gpu/drm/xe/xe_printk.h
+++ b/drivers/gpu/drm/xe/xe_printk.h
@@ -27,6 +27,9 @@
#define xe_warn(_xe, _fmt, ...) \
xe_printk((_xe), warn, _fmt, ##__VA_ARGS__)
+#define xe_warn_once(_xe, _fmt, ...) \
+ xe_printk((_xe), warn_once, _fmt, ##__VA_ARGS__)
+
#define xe_notice(_xe, _fmt, ...) \
xe_printk((_xe), notice, _fmt, ##__VA_ARGS__)
--
2.53.0
next prev parent reply other threads:[~2026-09-02 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 19:58 [PATCH v6 0/3] drm/xe: Refactor I2C and HECI error messages Jonathan Cavitt
2026-09-02 19:58 ` Jonathan Cavitt [this message]
2026-09-02 19:58 ` [PATCH v6 2/3] drm/xe/heci: Use xe print functions in xe_heci_gsc.c Jonathan Cavitt
2026-09-02 19:58 ` [PATCH v6 3/3] drm/xe/i2c: Use xe print functions in xe_i2c.c Jonathan Cavitt
2026-09-02 20:06 ` ✓ CI.KUnit: success for drm/xe: Refactor I2C and HECI error messages Patchwork
2026-09-02 21:02 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-03 11:32 ` ✗ Xe.CI.FULL: failure " Patchwork
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=20260902195851.306669-2-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@intel.com \
--cc=alex.zuo@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=raag.jadav@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.