Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Radhakrishna Sripada" <radhakrishna.sripada@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Initial Meteorlake Support (rev10)
Date: Fri, 16 Sep 2022 03:41:57 -0000	[thread overview]
Message-ID: <166329971793.18047.12349253401682027054@emeril.freedesktop.org> (raw)
In-Reply-To: <20220916014648.1310346-1-radhakrishna.sripada@intel.com>

== Series Details ==

Series: Initial Meteorlake Support (rev10)
URL   : https://patchwork.freedesktop.org/series/106786/
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-09-16  3:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16  1:46 [Intel-gfx] [PATCH v6 0/3] Initial Meteorlake Support Radhakrishna Sripada
2022-09-16  1:46 ` [Intel-gfx] [PATCH v6 1/3] drm/i915: Read graphics/media/display arch version from hw Radhakrishna Sripada
2022-09-23 17:40   ` Lucas De Marchi
2022-09-16  1:46 ` [Intel-gfx] [PATCH v6 2/3] drm/i915: Parse and set stepping for platforms with GMD Radhakrishna Sripada
2022-09-23 17:45   ` Lucas De Marchi
2022-09-16  1:46 ` [Intel-gfx] [PATCH v6 3/3] drm/i915/mtl: Define engine context layouts Radhakrishna Sripada
2022-09-23 22:48   ` Lucas De Marchi
2022-09-23 23:35     ` Matt Roper
2022-09-26 21:43   ` [Intel-gfx] [PATCH v4.1] " Radhakrishna Sripada
2022-09-16  3:41 ` Patchwork [this message]
2022-09-16  4:03 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Initial Meteorlake Support (rev10) Patchwork
2022-09-16  9:27 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-09-27  1:33 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Initial Meteorlake Support (rev11) 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=166329971793.18047.12349253401682027054@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=radhakrishna.sripada@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