All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Split out intel_vtd_active and run_as_guest to own header
Date: Tue, 22 Mar 2022 17:06:23 -0000	[thread overview]
Message-ID: <164796878355.20007.2887624057155984392@emeril.freedesktop.org> (raw)
In-Reply-To: <20220322164446.2124983-1-tvrtko.ursulin@linux.intel.com>

== Series Details ==

Series: drm/i915: Split out intel_vtd_active and run_as_guest to own header
URL   : https://patchwork.freedesktop.org/series/101646/
State : warning

== Summary ==

$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.



  parent reply	other threads:[~2022-03-22 17:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 16:44 [RFC] drm/i915: Split out intel_vtd_active and run_as_guest to own header Tvrtko Ursulin
2022-03-22 16:44 ` [Intel-gfx] " Tvrtko Ursulin
2022-03-22 17:05 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-03-22 17:06 ` Patchwork [this message]
2022-03-22 17:10 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-22 17:40 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-23  1:03 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-03-24  9:31 ` [RFC] " Jani Nikula
2022-03-24  9:31   ` [Intel-gfx] " Jani Nikula
2022-03-24  9:32   ` Jani Nikula
2022-03-24  9:32     ` [Intel-gfx] " Jani Nikula
2022-03-24 11:48   ` Tvrtko Ursulin
2022-03-24 11:48     ` [Intel-gfx] " Tvrtko Ursulin
2022-03-24 11:57     ` Jani Nikula
2022-03-24 11:57       ` [Intel-gfx] " Jani Nikula
2022-03-24 13:29       ` Tvrtko Ursulin
2022-03-24 13:29         ` [Intel-gfx] " Tvrtko Ursulin
2022-03-24 18:57         ` Jani Nikula
2022-03-24 18:57           ` [Intel-gfx] " Jani Nikula
2022-03-25  8:47           ` Tvrtko Ursulin
2022-03-25  8:47             ` [Intel-gfx] " Tvrtko Ursulin
2022-03-25 12:09             ` Jani Nikula
2022-03-25 12:09               ` [Intel-gfx] " Jani Nikula
2022-03-28 20:48               ` Lucas De Marchi
2022-03-28 20:48                 ` [Intel-gfx] " Lucas De Marchi

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=164796878355.20007.2887624057155984392@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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.