From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jani Nikula" <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: move i915_coherent_map_type() to i915_gem_pages.c and un-inline
Date: Wed, 14 Sep 2022 18:33:21 -0000 [thread overview]
Message-ID: <166318040159.30164.10863141047321879624@emeril.freedesktop.org> (raw)
In-Reply-To: <20220914163514.1837467-1-jani.nikula@intel.com>
== Series Details ==
Series: drm/i915: move i915_coherent_map_type() to i915_gem_pages.c and un-inline
URL : https://patchwork.freedesktop.org/series/108569/
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-14 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 16:35 [Intel-gfx] [PATCH] drm/i915: move i915_coherent_map_type() to i915_gem_pages.c and un-inline Jani Nikula
2022-09-14 18:33 ` Patchwork [this message]
2022-09-14 18:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-09-15 7:49 ` [Intel-gfx] [PATCH] " Tvrtko Ursulin
2022-09-20 16:59 ` Matthew Auld
2022-09-26 10:05 ` Jani Nikula
2022-09-15 11:30 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " 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=166318040159.30164.10863141047321879624@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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