From: Raag Jadav <raag.jadav@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
saurabhg.gupta@intel.com, alex.zuo@intel.com,
Michal.Wajdeczko@intel.com
Subject: Re: [PATCH v3 3/5] drm/xe/i2c: Use xe print functions in xe_i2c.c
Date: Sat, 6 Jun 2026 08:15:53 +0200 [thread overview]
Message-ID: <aiO7GVR1Zp31wDWd@black.igk.intel.com> (raw)
In-Reply-To: <20260605210534.3843211-4-jonathan.cavitt@intel.com>
On Sat, Jun 06, 2026 at 05:05:32AM +0800, Jonathan Cavitt wrote:
> Update xe_i2c.c to use the xe error reporting helper functions in
> xe_printk.h instead of directly calling the associated drm print
> functions from drm_print.h
>
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
Reviewed-by: Raag Jadav <raag.jadav@intel.com>
next prev parent reply other threads:[~2026-06-06 6:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 21:05 [PATCH v3 0/5] drm/{i915, xe}: Refactor generic_handle_irq_safe() error messages Jonathan Cavitt
2026-06-05 21:05 ` [PATCH v3 1/5] drm/xe/printk: Add xe_warn_once() Jonathan Cavitt
2026-06-05 21:05 ` [PATCH v3 2/5] drm/xe/heci: Use xe print functions in xe_heci_gsc.c Jonathan Cavitt
2026-06-06 10:30 ` Michal Wajdeczko
2026-06-05 21:05 ` [PATCH v3 3/5] drm/xe/i2c: Use xe print functions in xe_i2c.c Jonathan Cavitt
2026-06-06 6:15 ` Raag Jadav [this message]
2026-06-05 21:05 ` [PATCH v3 4/5] drm/i915: Refactor generic_handle_irq_safe() error messages Jonathan Cavitt
2026-06-05 21:05 ` [PATCH v3 5/5] drm/xe/i2c: Report i2c irq handler issue Jonathan Cavitt
2026-06-06 6:18 ` Raag Jadav
2026-06-06 10:39 ` Michal Wajdeczko
2026-06-08 14:34 ` Cavitt, Jonathan
2026-06-08 15:20 ` Raag Jadav
2026-06-05 22:18 ` ✓ i915.CI.BAT: success for drm/{i915, xe}: Refactor generic_handle_irq_safe() error messages (rev4) Patchwork
2026-06-06 15:30 ` ✗ i915.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=aiO7GVR1Zp31wDWd@black.igk.intel.com \
--to=raag.jadav@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=jonathan.cavitt@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