From: Petri Latvala <petri.latvala@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] intel-ci/blacklist: Exclude gem_exec_parse lri
Date: Fri, 11 Jan 2019 12:02:11 +0200 [thread overview]
Message-ID: <20190111100211.GY17124@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20190107164015.32438-1-chris@chris-wilson.co.uk>
On Mon, Jan 07, 2019 at 04:40:15PM +0000, Chris Wilson wrote:
> These exercise a certain HW misfeature, no longer protected by the
> kernel cmdparser due to obsolete userspace requirements.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> ---
> tests/intel-ci/blacklist.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
> index 73d127603..0c6b87695 100644
> --- a/tests/intel-ci/blacklist.txt
> +++ b/tests/intel-ci/blacklist.txt
> @@ -35,6 +35,7 @@ igt@gem_exec_gttfill@(?!.*basic).*
> igt@gem_exec_latency(@.*)?
> igt@gem_exec_lut_handle(@.*)?
> igt@gem_exec_nop@(?!.*(basic|signal-all)).*
> +igt@gem_exec_parse@.*lri.*
> igt@gem_exec_reloc@(?!.*basic).*
> igt@gem_exec_suspend@(?!.*basic).*
> igt@gem_exec_whisper@(?!normal$).*
Put this in a separate section with a comment (commit message seems
sufficient) that explains why it's blacklisted.
With that,
Acked-by: Petri Latvala <petri.latvala@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-01-11 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 16:40 [igt-dev] [PATCH i-g-t] intel-ci/blacklist: Exclude gem_exec_parse lri Chris Wilson
2019-01-07 17:12 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-01-07 21:02 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-01-11 10:02 ` Petri Latvala [this message]
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=20190111100211.GY17124@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox