From: Petri Latvala <petri.latvala@intel.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: Liviu Dudau <liviu.dudau@arm.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
IGT development <igt-dev@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>,
Alex Deucher <alexander.deucher@amd.com>,
Dave Airlie <airlied@redhat.com>, Sean Paul <sean@poorly.run>
Subject: Re: [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff mandatory
Date: Thu, 17 Jan 2019 13:09:07 +0200 [thread overview]
Message-ID: <20190117110907.GE17124@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20190117110100.hzngqk4faiuv6gam@ahiler-desk1.fi.intel.com>
On Thu, Jan 17, 2019 at 01:01:00PM +0200, Arkadiusz Hiler wrote:
> On Wed, Jan 16, 2019 at 05:39:03PM +0100, Daniel Vetter wrote:
> > Compared to the RFC[1] no changes to the patch itself, but igt moved
> > forward a lot:
> >
> > - gitlab CI builds with: reduced configs/libraries, arm cross build
> > and a sysroot build (should address all the build/cross platform
> > concerns raised in the RFC discussions).
> >
> > - tests reorganized into subdirectories so that the i915-gem tests
> > don't clog the main/shared tests directory anymore
> >
> > - quite a few more non-intel people contributing/reviewing/committing
> > igt tests patches.
> >
> > I think this addresses all the concerns raised in the RFC discussions,
> > and assuming there's enough Acks and no new issues that pop up, we can
> > go ahead with this.
> >
> > 1: https://patchwork.kernel.org/patch/10648851/
> > Cc: Petri Latvala <petri.latvala@intel.com>
> > Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> > Cc: Liviu Dudau <liviu.dudau@arm.com>
> > Cc: Sean Paul <sean@poorly.run>
> > Cc: Eric Anholt <eric@anholt.net>
> > Cc: Alex Deucher <alexander.deucher@amd.com>
> > Cc: Dave Airlie <airlied@redhat.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
>
> Thanks for the trust! I hope we will serve the subsystem well.
>
> I am happy about the influx of people from outside of i915 that we have
> got in 2018 and I hope it will only get better this year.
>
> There are still some cleanup tasks left when it comes driver-specific
> test compartmentalization, but we are getting there :-)
>
> Acked-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
+1
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
next prev parent reply other threads:[~2019-01-17 11:09 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 [this message]
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
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=20190117110907.GE17124@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=arkadiusz.hiler@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=liviu.dudau@arm.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