From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: "Nikula, Jani" <jani.nikula@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Provision to ignore long HPDs in CI systems (rev2)
Date: Mon, 10 Oct 2022 09:01:05 +0000 [thread overview]
Message-ID: <2a76afa9e7c843e85f8a3a270194c68b38465a11.camel@intel.com> (raw)
In-Reply-To: <166539195136.29673.16059547637667935229@emeril.freedesktop.org>
When tried locally, dim sparse were ok!
---
Sparse version: 0.6.4 (Ubuntu: 0.6.4-2)
Commit: drm/i915/display: ignore long HPDs based on a flag
Okay!
Commit: drm/i915/display: debugfs entry to control ignore long hpd flag
Okay!
-------
BR
vinod
On Mon, 2022-10-10 at 08:52 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: Provision to ignore long HPDs in CI systems (rev2)
> URL : https://patchwork.freedesktop.org/series/109475/
> 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-10-10 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 8:34 [Intel-gfx] [PATCH v2 0/2] Provision to ignore long HPDs in CI systems Vinod Govindapillai
2022-10-10 8:34 ` [Intel-gfx] [PATCH v2 1/2] drm/i915/display: ignore long HPDs based on a flag Vinod Govindapillai
2022-10-10 12:08 ` Andrzej Hajda
2022-10-10 12:11 ` Govindapillai, Vinod
2022-10-10 8:34 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/display: debugfs entry to control ignore long hpd flag Vinod Govindapillai
2022-10-10 12:10 ` Andrzej Hajda
2022-10-10 8:52 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Provision to ignore long HPDs in CI systems (rev2) Patchwork
2022-10-10 9:01 ` Govindapillai, Vinod [this message]
2022-10-10 9:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-10 12:13 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=2a76afa9e7c843e85f8a3a270194c68b38465a11.camel@intel.com \
--to=vinod.govindapillai@intel.com \
--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