From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Michael Cheng" <michael.cheng@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use drm_clflush* instead of clflush (rev8)
Date: Thu, 10 Feb 2022 01:39:45 -0000 [thread overview]
Message-ID: <164445718579.24640.12671596899928462314@emeril.freedesktop.org> (raw)
In-Reply-To: <20220210012617.1061641-1-michael.cheng@intel.com>
== Series Details ==
Series: Use drm_clflush* instead of clflush (rev8)
URL : https://patchwork.freedesktop.org/series/99450/
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-02-10 1:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 1:26 [PATCH v9 0/6] Use drm_clflush* instead of clflush Michael Cheng
2022-02-10 1:26 ` [Intel-gfx] " Michael Cheng
2022-02-10 1:26 ` [PATCH v9 1/6] drm: Add arch arm64 for drm_clflush_virt_range Michael Cheng
2022-02-10 1:26 ` [Intel-gfx] " Michael Cheng
2022-02-10 10:31 ` Tvrtko Ursulin
2022-02-10 10:31 ` Tvrtko Ursulin
2022-02-10 1:26 ` [PATCH v9 2/6] drm/i915/gt: Re-work intel_write_status_page Michael Cheng
2022-02-10 1:26 ` [Intel-gfx] " Michael Cheng
2022-02-10 1:26 ` [PATCH v9 3/6] drm/i915/gt: Drop invalidate_csb_entries Michael Cheng
2022-02-10 1:26 ` [Intel-gfx] " Michael Cheng
2022-02-10 1:26 ` [PATCH v9 4/6] drm/i915/gt: Re-work reset_csb Michael Cheng
2022-02-10 1:26 ` [Intel-gfx] " Michael Cheng
2022-02-10 1:26 ` [PATCH v9 5/6] drm/i915/: Re-work clflush_write32 Michael Cheng
2022-02-10 1:26 ` [Intel-gfx] " Michael Cheng
2022-02-10 1:26 ` [PATCH v9 6/6] drm/i915/gt: replace cache_clflush_range Michael Cheng
2022-02-10 1:26 ` [Intel-gfx] " Michael Cheng
2022-02-10 1:38 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev8) Patchwork
2022-02-10 1:39 ` Patchwork [this message]
2022-02-10 2:12 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=164445718579.24640.12671596899928462314@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michael.cheng@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.