From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Stone <daniel@fooishbar.org>,
"Wentland, Harry" <Harry.Wentland@amd.com>
Cc: Petri Latvala <petri.latvala@intel.com>,
Liviu Dudau <liviu.dudau@arm.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
IGT development <igt-dev@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Sean Paul <sean@poorly.run>
Subject: Re: [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff mandatory
Date: Wed, 23 Jan 2019 12:11:36 +0200 [thread overview]
Message-ID: <87h8dz3cpz.fsf@intel.com> (raw)
In-Reply-To: <CAPj87rNr2TM7mJv3xN2bLLsh+A0KZ-23rFt-EMtHmWHuBf2DMQ@mail.gmail.com>
On Wed, 23 Jan 2019, Daniel Stone <daniel@fooishbar.org> wrote:
> If it helps, maybe we could draw up a list somewhere (README in igt?
> wiki?) of which tests seem to pass generically across a few drivers,
> which ones are expected to pass, which ones don't but really should,
> etc. I'm currently running on imx-drm (complicated by hitting a
> page-cache BUG!), and a couple of others are getting results from
> rockchip, vc4, and msm. Those are pretty well supported and actively
> maintained, so should give us a decent first cut at such a list.
See tests/intel-ci/README. igt supports test lists, we could maintain
similar lists for different needs.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-01-23 10:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 16:39 [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff mandatory Daniel Vetter
2019-01-16 22:41 ` Eric Anholt
2019-01-17 11:50 ` Daniel Vetter
2019-01-17 11:01 ` Arkadiusz Hiler
2019-01-17 11:09 ` Petri Latvala
2019-01-17 11:38 ` Liviu Dudau
2019-01-17 11:52 ` Daniel Vetter
2019-01-17 12:26 ` Liviu Dudau
2019-01-17 12:32 ` Daniel Vetter
2019-01-17 14:54 ` Liviu Dudau
2019-01-17 15:59 ` Daniel Vetter
2019-01-18 11:19 ` Liviu Dudau
2019-01-21 11:54 ` Brian Starkey
2019-01-21 17:21 ` Daniel Vetter
2019-01-22 8:53 ` [igt-dev] " Daniel Vetter
2019-01-22 13:27 ` Brian Starkey
2019-01-22 14:03 ` Daniel Vetter
2019-01-22 15:08 ` Brian Starkey
2019-01-22 15:17 ` Daniel Vetter
2019-01-22 16:11 ` Sean Paul
2019-01-22 16:28 ` Daniel Vetter
2019-01-28 14:03 ` Liviu Dudau
2019-01-28 17:21 ` Daniel Vetter
2019-01-22 19:00 ` Wentland, Harry
2019-01-22 19:19 ` Daniel Vetter
2019-01-22 19:42 ` Wentland, Harry
2019-01-22 19:53 ` Sean Paul
2019-01-23 9:46 ` Brian Starkey
2019-01-23 10:03 ` Daniel Stone
2019-01-23 10:11 ` Jani Nikula [this message]
2019-01-23 10:53 ` Daniel Vetter
2019-01-23 10:03 ` Jani Nikula
2019-01-23 10:54 ` Daniel Vetter
2019-01-23 9:40 ` Brian Starkey
2019-01-23 10:50 ` Daniel Vetter
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=87h8dz3cpz.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Alexander.Deucher@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@intel.com \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=liviu.dudau@arm.com \
--cc=petri.latvala@intel.com \
--cc=sean@poorly.run \
/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