From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: DRI Development <dri-devel@lists.freedesktop.org>,
IGT development <igt-dev@lists.freedesktop.org>
Cc: Petri Latvala <petri.latvala@intel.com>,
Liviu Dudau <liviu.dudau@arm.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Alex Deucher <alexander.deucher@amd.com>,
Dave Airlie <airlied@redhat.com>, Sean Paul <sean@poorly.run>
Subject: [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff mandatory
Date: Wed, 16 Jan 2019 17:39:03 +0100 [thread overview]
Message-ID: <20190116163903.12785-1-daniel.vetter@ffwll.ch> (raw)
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>
---
Documentation/gpu/drm-uapi.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
index a752aa561ea4..413915d6b7d2 100644
--- a/Documentation/gpu/drm-uapi.rst
+++ b/Documentation/gpu/drm-uapi.rst
@@ -238,6 +238,13 @@ DRM specific patterns. Note that ENOTTY has the slightly unintuitive meaning of
Testing and validation
======================
+Testing Requirements for userspace API
+--------------------------------------
+
+New cross-driver userspace interface extensions, like new IOCTL, new KMS
+properties, new files in sysfs or anything else that constitutes an API change
+need to have driver-agnostic testcases in IGT for that feature.
+
Validating changes with IGT
---------------------------
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-01-16 18:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 16:39 Daniel Vetter [this message]
2019-01-16 22:41 ` [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff mandatory 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
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=20190116163903.12785-1-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=daniel.vetter@intel.com \
--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