All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Adrian Larumbe" <adrian.larumbe@collabora.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Change semantics of context isolation reporting to UM (rev2)
Date: Fri, 29 Apr 2022 17:19:29 -0000	[thread overview]
Message-ID: <165125276910.1654.3945165891242194862@emeril.freedesktop.org> (raw)
In-Reply-To: <20220429151112.1041959-1-adrian.larumbe@collabora.com>

== Series Details ==

Series: drm/i915: Change semantics of context isolation reporting to UM (rev2)
URL   : https://patchwork.freedesktop.org/series/103343/
State : warning

== Summary ==

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



  reply	other threads:[~2022-04-29 17:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 15:11 [Intel-gfx] [PATCH] drm/i915: Change semantics of context isolation reporting to UM Adrian Larumbe
2022-04-29 17:19 ` Patchwork [this message]
2022-04-29 17:51 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Change semantics of context isolation reporting to UM (rev2) Patchwork
2022-05-03 14:44 ` [Intel-gfx] [PATCH] drm/i915: Change semantics of context isolation reporting to UM Tvrtko Ursulin
2022-05-04 11:50   ` Adrian Larumbe
2022-05-04 12:24 ` Daniel Vetter
2022-05-04 12:24   ` [Intel-gfx] " Daniel Vetter
2022-05-04 14:59   ` Matt Roper
2022-05-04 14:59     ` [Intel-gfx] " Matt Roper
2022-05-04 16:42     ` Daniel Vetter
2022-05-04 16:42       ` [Intel-gfx] " Daniel Vetter
2022-05-04 18:12       ` Matt Roper
2022-05-04 18:12         ` [Intel-gfx] " Matt Roper
2022-05-05 12:46         ` Daniel Vetter
2022-05-05 12:46           ` [Intel-gfx] " Daniel Vetter

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=165125276910.1654.3945165891242194862@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=adrian.larumbe@collabora.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.