From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jani Nikula" <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/ipc: ipc and sub-struct refactoring, take 2
Date: Mon, 12 Sep 2022 18:27:37 -0000 [thread overview]
Message-ID: <166300725716.11337.8091745409696427673@emeril.freedesktop.org> (raw)
In-Reply-To: <cover.1662983005.git.jani.nikula@intel.com>
== Series Details ==
Series: drm/i915/ipc: ipc and sub-struct refactoring, take 2
URL : https://patchwork.freedesktop.org/series/108428/
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-09-12 18:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 11:45 [Intel-gfx] [PATCH 0/5] drm/i915/ipc: ipc and sub-struct refactoring, take 2 Jani Nikula
2022-09-12 11:45 ` [Intel-gfx] [PATCH 1/5] drm/i915/ipc: refactor and rename IPC functions Jani Nikula
2022-09-13 9:23 ` Ville Syrjälä
2022-09-13 17:09 ` Jani Nikula
2022-09-12 11:45 ` [Intel-gfx] [PATCH 2/5] drm/i915/ipc: move IPC debugfs to skl_watermark.c Jani Nikula
2022-09-12 11:45 ` [Intel-gfx] [PATCH 3/5] drm/i915/ipc: register debugfs only if IPC available Jani Nikula
2022-09-12 11:45 ` [Intel-gfx] [PATCH 4/5] drm/i915/display: move IPC under display wm sub-struct Jani Nikula
2022-09-12 11:45 ` [Intel-gfx] [PATCH 5/5] drm/i915/ipc: use intel_uncore_rmw() to enable/disable Jani Nikula
2022-09-12 18:27 ` Patchwork [this message]
2022-09-12 18:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/ipc: ipc and sub-struct refactoring, take 2 Patchwork
2022-09-13 7:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/ipc: ipc and sub-struct refactoring, take 2 (rev2) Patchwork
2022-09-13 16:22 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=166300725716.11337.8091745409696427673@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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