From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [CI v3 0/6] drm/i915: error capture cleanups and refactor
Date: Mon, 14 Apr 2025 21:46:49 +0300 [thread overview]
Message-ID: <8734eatwbq.fsf@intel.com> (raw)
In-Reply-To: <cover.1744630147.git.jani.nikula@intel.com>
On Mon, 14 Apr 2025, Jani Nikula <jani.nikula@intel.com> wrote:
> Resend for clean CI.
And pushed to din, thanks for the review.
>
> Jani Nikula (6):
> drm/i915: use 32-bit access for gen2 irq registers
> drm/i915: record GEN2_IER in gtier[0] for pre-ilk error capture
> drm/i915: stop recording IER in error capture
> drm/i915: use display snapshot mechanism for display irq regs
> drm/i915: don't capture DERRMR for VLV/CHV
> drm/i915: use graphics version instead of PCH split in error capture
>
> .../gpu/drm/i915/display/intel_display_irq.c | 28 +++++++++++++++
> .../gpu/drm/i915/display/intel_display_irq.h | 5 +++
> .../drm/i915/display/intel_display_snapshot.c | 5 +++
> drivers/gpu/drm/i915/i915_gpu_error.c | 35 +++----------------
> drivers/gpu/drm/i915/i915_gpu_error.h | 3 --
> 5 files changed, 42 insertions(+), 34 deletions(-)
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-04-14 18:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 11:29 [CI v3 0/6] drm/i915: error capture cleanups and refactor Jani Nikula
2025-04-14 11:29 ` [CI v3 1/6] drm/i915: use 32-bit access for gen2 irq registers Jani Nikula
2025-04-14 11:29 ` [CI v3 2/6] drm/i915: record GEN2_IER in gtier[0] for pre-ilk error capture Jani Nikula
2025-04-14 11:29 ` [CI v3 3/6] drm/i915: stop recording IER in " Jani Nikula
2025-04-14 11:29 ` [CI v3 4/6] drm/i915: use display snapshot mechanism for display irq regs Jani Nikula
2025-04-14 11:29 ` [CI v3 5/6] drm/i915: don't capture DERRMR for VLV/CHV Jani Nikula
2025-04-14 11:29 ` [CI v3 6/6] drm/i915: use graphics version instead of PCH split in error capture Jani Nikula
2025-04-14 12:17 ` ✓ CI.Patch_applied: success for drm/i915: error capture cleanups and refactor Patchwork
2025-04-14 12:18 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-14 12:19 ` ✓ CI.KUnit: success " Patchwork
2025-04-14 12:27 ` ✓ CI.Build: " Patchwork
2025-04-14 12:30 ` ✓ CI.Hooks: " Patchwork
2025-04-14 12:38 ` ✗ CI.checksparse: warning " Patchwork
2025-04-14 13:30 ` ✓ Xe.CI.BAT: success " Patchwork
2025-04-14 14:46 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2025-04-14 14:46 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-04-14 15:07 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-14 17:13 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-14 18:26 ` ✗ i915.CI.Full: " Patchwork
2025-04-14 18:46 ` Jani Nikula [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=8734eatwbq.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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.