From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: saurabhg.gupta@intel.com, alex.zuo@intel.com,
jonathan.cavitt@intel.com, raag.jadav@intel.com,
Michal.Wajdeczko@intel.com
Subject: [PATCH v2 1/5] drm/xe/printk: Add xe_warn_once()
Date: Sat, 6 Jun 2026 04:40:43 +0800 [thread overview]
Message-ID: <20260605204047.3840459-2-jonathan.cavitt@intel.com> (raw)
In-Reply-To: <20260605204047.3840459-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 c5be2385aa95..afa787fcdeb6 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-06-05 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 20:40 [PATCH v2 0/5] drm/{i915, xe}: Refactor generic_handle_irq_safe() error messages Jonathan Cavitt
2026-06-05 20:40 ` Jonathan Cavitt [this message]
2026-06-05 20:40 ` [PATCH v2 2/5] drm/xe/heci: Use xe print functions in xe_heci_gsc.c Jonathan Cavitt
2026-06-05 20:40 ` [PATCH v2 3/5] drm/xe/i2c: Use xe print functions in xe_i2c.c Jonathan Cavitt
2026-06-05 20:40 ` [PATCH v2 4/5] drm/i915: Refactor generic_handle_irq_safe() error messages Jonathan Cavitt
2026-06-05 20:40 ` [PATCH v2 5/5] drm/xe/i2c: Report i2c irq handler issue Jonathan Cavitt
2026-06-05 21:01 ` ✗ Fi.CI.BUILD: failure for drm/{i915, xe}: Refactor generic_handle_irq_safe() error messages (rev3) 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=20260605204047.3840459-2-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@intel.com \
--cc=Michal.Wajdeczko@intel.com \
--cc=alex.zuo@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=raag.jadav@intel.com \
--cc=saurabhg.gupta@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox