From: Petri Latvala <petri.latvala@intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v2] ts/core_setmaster: new test for drop/set master semantics
Date: Fri, 21 Feb 2020 14:19:05 +0200 [thread overview]
Message-ID: <20200221121905.GG25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20200221115825.GF25209@platvala-desk.ger.corp.intel.com>
On Fri, Feb 21, 2020 at 01:58:25PM +0200, Petri Latvala wrote:
> Wrapping all that in an igt_subtest_group not required but could be
> used to communicate to human readers that this is the subtest these
> two fixtures are for.
Correction, it is required if you use igt_require with chmod().
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-02-21 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 14:24 [igt-dev] [PATCH i-g-t v2] ts/core_setmaster: new test for drop/set master semantics Emil Velikov
2020-02-19 15:41 ` [igt-dev] ✗ GitLab.Pipeline: failure for ts/core_setmaster: new test for drop/set master semantics (rev2) Patchwork
2020-02-19 15:59 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-02-19 16:20 ` [igt-dev] [PATCH i-g-t v2] ts/core_setmaster: new test for drop/set master semantics Emil Velikov
2020-02-21 9:30 ` [igt-dev] ✓ Fi.CI.IGT: success for ts/core_setmaster: new test for drop/set master semantics (rev2) Patchwork
2020-02-21 11:36 ` Emil Velikov
2020-02-21 11:58 ` [igt-dev] [PATCH i-g-t v2] ts/core_setmaster: new test for drop/set master semantics Petri Latvala
2020-02-21 12:19 ` Petri Latvala [this message]
2020-02-21 13:55 ` Emil Velikov
2020-02-24 8:49 ` Petri Latvala
2020-02-24 11:57 ` Emil Velikov
2020-02-25 9:10 ` Petri Latvala
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=20200221121905.GG25209@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=emil.l.velikov@gmail.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