public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/1] Rename dynamic subtest blocks
Date: Tue, 19 Nov 2019 13:53:39 +0200	[thread overview]
Message-ID: <20191119115339.GA25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <157409582632.2240.10570647267359058952@emeril.freedesktop.org>

On Mon, Nov 18, 2019 at 04:50:26PM +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: series starting with [i-g-t,1/1] Rename dynamic subtest blocks
> URL   : https://patchwork.freedesktop.org/series/69622/
> State : success


Thanks for the acks, this has now been merged.

The conversion to dynamic subtests for i915 engines is tracked in
https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/44 and will
happen one binary at a time, as there's going to be a lot of renaming,
to get cibuglog filters renamed in sync. And at least one part of
dynamic subtest framework needs changing before _that_ can begin, so
stay tuned.

After engines, kernel selftest launchers get their turn, and at some
point, KMS pipes.



-- 
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      reply	other threads:[~2019-11-19 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18 11:09 [igt-dev] [PATCH i-g-t 1/1] Rename dynamic subtest blocks Petri Latvala
2019-11-18 11:16 ` Chris Wilson
2019-11-18 11:50 ` Tvrtko Ursulin
2019-11-18 12:40 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/1] " Patchwork
2019-11-18 13:02 ` [igt-dev] [PATCH i-g-t 1/1] " Arkadiusz Hiler
2019-11-18 16:50 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/1] " Patchwork
2019-11-19 11:53   ` 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=20191119115339.GA25209@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=igt-dev@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