From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/gt: Expose per gt defaults in sysfs
Date: Thu, 26 May 2022 19:30:20 -0000 [thread overview]
Message-ID: <165359342094.19748.15112134393500889129@emeril.freedesktop.org> (raw)
In-Reply-To: <cover.1653591227.git.ashutosh.dixit@intel.com>
== Series Details ==
Series: drm/i915/gt: Expose per gt defaults in sysfs
URL : https://patchwork.freedesktop.org/series/104423/
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-05-26 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 19:00 [Intel-gfx] [PATCH v2 0/3] drm/i915/gt: Expose per gt defaults in sysfs Ashutosh Dixit
2022-05-26 19:00 ` [Intel-gfx] [PATCH 1/3] drm/i915/gt: Create gt/gtN/.defaults for per gt sysfs defaults Ashutosh Dixit
2022-05-26 19:00 ` [Intel-gfx] [PATCH 2/3] drm/i915/gt: Expose per-gt RPS defaults in sysfs Ashutosh Dixit
2022-05-26 19:00 ` [Intel-gfx] [PATCH 3/3] drm/i915/gt: Expose default value for media_freq_factor in per-gt sysfs Ashutosh Dixit
2022-05-26 19:30 ` Patchwork [this message]
2022-05-26 21:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: Expose per gt defaults in sysfs Patchwork
2022-05-27 0:26 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-27 23:41 ` [Intel-gfx] [PATCH v2 0/3] " Matt Roper
2022-06-02 23:36 ` Dixit, Ashutosh
2022-06-02 23:55 ` Matt Roper
2022-06-03 2:25 ` Dixit, Ashutosh
2022-07-19 1:09 ` Dixit, Ashutosh
2022-07-19 1:09 ` Dixit, Ashutosh
-- strict thread matches above, loose matches on Subject: below --
2022-07-19 1:07 [PATCH 0/2] " Ashutosh Dixit
2022-07-19 1:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-05-26 18:35 [Intel-gfx] [PATCH 0/2] " Ashutosh Dixit
2022-05-26 18:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning 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=165359342094.19748.15112134393500889129@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=ashutosh.dixit@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.