From: Maxime Ripard <maxime.ripard@bootlin.com>
To: intel-gfx@lists.freedesktop.org, eben@raspberrypi.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [RFC PATCH i-g-t 3/3] tests: Add vc4 test suite
Date: Wed, 21 Mar 2018 11:41:32 +0100 [thread overview]
Message-ID: <20180321104132.bvzklwnff23pbwgp@flea> (raw)
In-Reply-To: <20180314104410.n4qa3hj775fyust2@platvala-desk.ger.corp.intel.com>
Hi,
On Wed, Mar 14, 2018 at 12:44:10PM +0200, Petri Latvala wrote:
> On Tue, Mar 13, 2018 at 04:18:54PM +0100, Maxime Ripard wrote:
> > Hi,
> >
> > On Tue, Mar 13, 2018 at 12:42:02PM +0200, Petri Latvala wrote:
> > > On Mon, Mar 05, 2018 at 03:21:29PM +0100, Maxime Ripard wrote:
> > > > Add some various test suites relevant for the vc4 drm driver.
> > > >
> > > > Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
> > > > ---
> > > > tests/vc4_ci/vc4-chamelium-fast.testlist | 4 ++++
> > > > tests/vc4_ci/vc4-chamelium.testlist | 9 ++++++++
> > > > tests/vc4_ci/vc4.testlist | 35 ++++++++++++++++++++++++++++++++
> > > > 3 files changed, 48 insertions(+)
> > > > create mode 100644 tests/vc4_ci/vc4-chamelium-fast.testlist
> > > > create mode 100644 tests/vc4_ci/vc4-chamelium.testlist
> > > > create mode 100644 tests/vc4_ci/vc4.testlist
> > >
> > > Can you also add a README explaining where vc4_ci results can be found
> > > (or statement for the lack of a public view) and how these testlist
> > > files are used?
> >
> > There isn't any publicly visible CI plan at the moment (that I know
> > of). This patch was more to get a list of meaningful tests into the
> > tree so that the various people involved could share the tests run for
> > now at least. I'm not sure what the policy is for that to be honest.
>
> From IGT's side the policy is that the people who need such a
> directory will set it up and it becomes their turf, in both
> directions. Their responsibility to maintain, and their ack is
> required for changes.
Ok, so I guess it would become mostly Eric's garden then :)
Eric, are you ok with such a test suite?
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-21 10:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 14:21 [RFC PATCH i-g-t 0/3] Test the plane formats on the Chamelium Maxime Ripard
2018-03-05 14:21 ` [RFC PATCH i-g-t 1/3] tests/chamelium: Move some functions and structures to a common place Maxime Ripard
2018-03-05 14:21 ` [RFC PATCH i-g-t 2/3] tests/chamelium: Add test case for plane formats Maxime Ripard
2018-03-12 19:02 ` Eric Anholt
2018-03-13 15:05 ` Maxime Ripard
2018-03-05 14:21 ` [RFC PATCH i-g-t 3/3] tests: Add vc4 test suite Maxime Ripard
2018-03-13 10:42 ` Petri Latvala
2018-03-13 15:18 ` Maxime Ripard
2018-03-14 10:44 ` Petri Latvala
2018-03-21 10:41 ` Maxime Ripard [this message]
2018-03-05 16:49 ` ✓ Fi.CI.BAT: success for Test the plane formats on the Chamelium Patchwork
2018-03-05 21:51 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-03-21 11:25 ` [RFC PATCH i-g-t 0/3] " Maxime Ripard
2018-03-21 17:10 ` Eric Anholt
2018-03-28 8:30 ` Maxime Ripard
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=20180321104132.bvzklwnff23pbwgp@flea \
--to=maxime.ripard@bootlin.com \
--cc=eben@raspberrypi.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.petazzoni@bootlin.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