From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Suraj Kandpal" <suraj.kandpal@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for i915 writeback private framework (rev5)
Date: Thu, 21 Apr 2022 05:35:21 -0000 [thread overview]
Message-ID: <165051932118.10764.13300023209483750145@emeril.freedesktop.org> (raw)
In-Reply-To: <20220421050756.2036609-1-suraj.kandpal@intel.com>
== Series Details ==
Series: i915 writeback private framework (rev5)
URL : https://patchwork.freedesktop.org/series/101425/
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-04-21 5:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 5:07 [RFC PATCH 0/3] i915 writeback private framework Suraj Kandpal
2022-04-21 5:07 ` [Intel-gfx] " Suraj Kandpal
2022-04-21 5:07 ` [RFC PATCH 1/3] drm/i915: Creating writeback pipeline to bypass drm_writeback framework Suraj Kandpal
2022-04-21 5:07 ` [Intel-gfx] " Suraj Kandpal
2022-04-28 5:52 ` Kandpal, Suraj
2022-04-28 5:52 ` [Intel-gfx] " Kandpal, Suraj
2022-04-21 5:07 ` [RFC PATCH 2/3] drm/i915: Define WD trancoder for i915 Suraj Kandpal
2022-04-21 5:07 ` [Intel-gfx] " Suraj Kandpal
2022-04-28 5:53 ` Kandpal, Suraj
2022-04-28 5:53 ` [Intel-gfx] " Kandpal, Suraj
2022-04-21 5:07 ` [RFC PATCH 3/3] drm/i915: Enabling WD Transcoder Suraj Kandpal
2022-04-21 5:07 ` [Intel-gfx] " Suraj Kandpal
2022-04-28 5:53 ` Kandpal, Suraj
2022-04-28 5:53 ` [Intel-gfx] " Kandpal, Suraj
2022-04-21 5:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915 writeback private framework (rev5) Patchwork
2022-04-21 5:35 ` Patchwork [this message]
2022-04-21 6:00 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-28 5:51 ` [RFC PATCH 0/3] i915 writeback private framework Kandpal, Suraj
2022-04-28 5:51 ` [Intel-gfx] " Kandpal, Suraj
2022-04-28 12:02 ` Laurent Pinchart
2022-04-28 12:02 ` [Intel-gfx] " Laurent Pinchart
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=165051932118.10764.13300023209483750145@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=suraj.kandpal@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.