All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Daniele Ceraolo Spurio" <daniele.ceraolospurio@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: prepare for uC loading on MTL (rev3)
Date: Sat, 22 Oct 2022 00:25:11 -0000	[thread overview]
Message-ID: <166639831145.27175.1292818980593164942@emeril.freedesktop.org> (raw)
In-Reply-To: <20221022001008.2340224-1-daniele.ceraolospurio@intel.com>

== Series Details ==

Series: drm/i915: prepare for uC loading on MTL (rev3)
URL   : https://patchwork.freedesktop.org/series/108925/
State : warning

== Summary ==

Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.



  parent reply	other threads:[~2022-10-22  0:25 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22  0:10 [PATCH v3 0/7] drm/i915: prepare for uC loading on MTL Daniele Ceraolo Spurio
2022-10-22  0:10 ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-10-22  0:10 ` [PATCH v3 1/7] drm/i915/huc: only load HuC on GTs that have VCS engines Daniele Ceraolo Spurio
2022-10-22  0:10   ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-10-22  0:10 ` [PATCH v3 2/7] drm/i915/uc: fetch uc firmwares for each GT Daniele Ceraolo Spurio
2022-10-22  0:10   ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-10-22  0:10 ` [PATCH v3 3/7] drm/i915/uc: use different ggtt pin offsets for uc loads Daniele Ceraolo Spurio
2022-10-22  0:10   ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-10-24 20:41   ` John Harrison
2022-10-24 20:41     ` [Intel-gfx] " John Harrison
2022-10-22  0:10 ` [PATCH v3 4/7] drm/i915/guc: Add GuC deprivilege feature to MTL Daniele Ceraolo Spurio
2022-10-22  0:10   ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-10-22  0:10 ` [PATCH v3 5/7] drm/i915/mtl: Handle wopcm per-GT and limit calculations Daniele Ceraolo Spurio
2022-10-22  0:10   ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-10-24 21:33   ` John Harrison
2022-10-24 21:33     ` [Intel-gfx] " John Harrison
2022-10-24 21:39     ` Ceraolo Spurio, Daniele
2022-10-24 21:39       ` [Intel-gfx] " Ceraolo Spurio, Daniele
2022-10-24 21:46       ` John Harrison
2022-10-24 21:46         ` [Intel-gfx] " John Harrison
2022-10-24 22:10         ` Ceraolo Spurio, Daniele
2022-10-24 22:10           ` [Intel-gfx] " Ceraolo Spurio, Daniele
2022-10-24 22:26   ` [PATCH] " Daniele Ceraolo Spurio
2022-10-24 22:26     ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-10-26  1:33     ` John Harrison
2022-10-26  1:33       ` [Intel-gfx] " John Harrison
2022-10-22  0:10 ` [PATCH v3 6/7] drm/i915/guc: define media GT GuC send regs Daniele Ceraolo Spurio
2022-10-22  0:10   ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-10-22  0:10 ` [PATCH v3 7/7] drm/i915/guc: handle interrupts from media GuC Daniele Ceraolo Spurio
2022-10-22  0:10   ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-10-24 20:28   ` Ceraolo Spurio, Daniele
2022-10-24 20:28     ` [Intel-gfx] " Ceraolo Spurio, Daniele
2022-10-22  0:25 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: prepare for uC loading on MTL (rev3) Patchwork
2022-10-22  0:25 ` Patchwork [this message]
2022-10-22  0:47 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-22 20:43 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-25  2:36 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: prepare for uC loading on MTL (rev4) Patchwork
2022-10-25  2:36 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-25  2:59 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-27  0:23 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: prepare for uC loading on MTL (rev5) Patchwork
2022-10-27  0:23 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-27  0:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-27 10:14 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-11-07 23:46 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: prepare for uC loading on MTL (rev6) 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=166639831145.27175.1292818980593164942@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-gfx@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.