From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Anshuman Gupta" <anshuman.gupta@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual
Date: Fri, 23 Sep 2022 17:02:11 -0000 [thread overview]
Message-ID: <166395253185.30117.8492594931214268972@emeril.freedesktop.org> (raw)
In-Reply-To: <20220923143125.5768-1-anshuman.gupta@intel.com>
== Series Details ==
Series: drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual
URL : https://patchwork.freedesktop.org/series/108972/
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-23 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 14:31 [Intel-gfx] [PATCH] drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual Anshuman Gupta
2022-09-23 17:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-09-23 17:02 ` Patchwork [this message]
2022-09-23 17:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-24 7:32 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-09-26 16:22 ` [Intel-gfx] [PATCH] " Matthew Auld
2022-09-27 12:30 ` Gupta, Anshuman
2022-09-27 12:45 ` Matthew Auld
2022-09-28 13:32 ` Gupta, Anshuman
2022-10-21 9:55 ` [Intel-gfx] [PATCH v2 1/2] drm/i915: Encapsulate lmem rpm stuff in intel_runtime_pm Anshuman Gupta
2022-10-21 9:55 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual Anshuman Gupta
2022-10-24 14:03 ` Matthew Auld
2022-10-24 14:00 ` [Intel-gfx] [PATCH v2 1/2] drm/i915: Encapsulate lmem rpm stuff in intel_runtime_pm Matthew Auld
2022-10-31 6:42 ` Gupta, Anshuman
2022-10-31 9:34 ` Rodrigo Vivi
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=166395253185.30117.8492594931214268972@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=anshuman.gupta@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.