From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Auld" <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/7] drm/i915/lmem: don't treat small BAR as an error
Date: Tue, 15 Mar 2022 20:04:28 -0000 [thread overview]
Message-ID: <164737466842.20491.6378532448078880222@emeril.freedesktop.org> (raw)
In-Reply-To: <20220315181425.576828-1-matthew.auld@intel.com>
== Series Details ==
Series: series starting with [CI,1/7] drm/i915/lmem: don't treat small BAR as an error
URL : https://patchwork.freedesktop.org/series/101398/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
next prev parent reply other threads:[~2022-03-15 20:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 18:14 [Intel-gfx] [CI 1/7] drm/i915/lmem: don't treat small BAR as an error Matthew Auld
2022-03-15 18:14 ` [Intel-gfx] [CI 2/7] drm/i915/stolen: " Matthew Auld
2022-03-15 18:14 ` [Intel-gfx] [CI 3/7] drm/i915/stolen: consider I915_BO_ALLOC_GPU_ONLY Matthew Auld
2022-03-15 18:14 ` [Intel-gfx] [CI 4/7] drm/i915: add i915_gem_object_create_region_at() Matthew Auld
2022-03-15 18:14 ` [Intel-gfx] [CI 5/7] drm/i915/ttm: wire up the object offset Matthew Auld
2022-03-15 18:14 ` [Intel-gfx] [CI 6/7] drm/i915/display: Check mappable aperture when pinning preallocated vma Matthew Auld
2022-03-15 18:14 ` [Intel-gfx] [CI 7/7] drm/i915: fixup the initial fb base on DGFX Matthew Auld
2022-03-15 20:04 ` Patchwork [this message]
2022-03-15 20:43 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/7] drm/i915/lmem: don't treat small BAR as an error Patchwork
2022-03-16 0:38 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-16 9:15 ` Matthew Auld
2022-03-16 16:50 ` Vudum, Lakshminarayana
2022-03-16 15:53 ` [Intel-gfx] ✓ Fi.CI.IGT: success " 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=164737466842.20491.6378532448078880222@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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.