From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matt Roper" <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for i915: PVC steppings and initial workarounds
Date: Sat, 28 May 2022 11:59:18 -0000 [thread overview]
Message-ID: <165373915898.24492.12937524531106197426@emeril.freedesktop.org> (raw)
In-Reply-To: <20220527163348.1936146-1-matthew.d.roper@intel.com>
== Series Details ==
Series: i915: PVC steppings and initial workarounds
URL : https://patchwork.freedesktop.org/series/104461/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
next prev parent reply other threads:[~2022-05-28 11:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 16:33 [PATCH 0/2] i915: PVC steppings and initial workarounds Matt Roper
2022-05-27 16:33 ` [Intel-gfx] " Matt Roper
2022-05-27 16:33 ` [PATCH 1/2] drm/i915/pvc: Extract stepping information from PCI revid Matt Roper
2022-05-27 16:33 ` [Intel-gfx] " Matt Roper
2022-05-31 21:33 ` Matt Atwood
2022-05-27 16:33 ` [PATCH 2/2] drm/i915/pvc: Add initial PVC workarounds Matt Roper
2022-05-27 16:33 ` [Intel-gfx] " Matt Roper
2022-05-31 21:36 ` Matt Atwood
2022-05-28 11:59 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: PVC steppings and initial workarounds Patchwork
2022-05-28 11:59 ` Patchwork [this message]
2022-05-28 12:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-05-28 12:35 ` Patchwork
2022-05-28 13:36 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-05-31 21:49 ` Matt Roper
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=165373915898.24492.12937524531106197426@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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.