From: Daniel Vetter <daniel@ffwll.ch>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: Petri Latvala <petri.latvala@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
IGT development <igt-dev@lists.freedesktop.org>,
VMware Graphics <linux-graphics-maintainer@vmware.com>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t 5/5] tests/kms_selftest: Integrate kernel selftest test-drm_modeset
Date: Tue, 25 Jun 2019 17:37:01 +0200 [thread overview]
Message-ID: <20190625153701.GA12905@phenom.ffwll.local> (raw)
In-Reply-To: <20190625060132.rsidgloshp7oz4ud@ahiler-desk1.fi.intel.com>
On Tue, Jun 25, 2019 at 09:01:32AM +0300, Arkadiusz Hiler wrote:
> On Thu, Jun 20, 2019 at 03:20:02PM +0200, Daniel Vetter wrote:
> > On Tue, Oct 16, 2018 at 03:23:41PM -0700, Deepak Rawat wrote:
> > > Call kernel selftest module test-drm_modeset for testing KMS.
> > >
> > > v2:
> > > - Add test alphabetically.
> > > - Add test to meson build.
> > >
> > > v3: Rename to kms_selftest.
> > >
> > > Signed-off-by: Deepak Rawat <drawat@vmware.com>
> >
> > Just realized that this never landed ... any reasons? Would be nice to get
> > this handled.
> >
> > Petri/Arek?
> >
> > Cheers, Daniel
>
> What do you mean by "this never landed"?
>
> https://gitlab.freedesktop.org/drm/igt-gpu-tools/commit/7766b1e2348b
>
> commit 7766b1e2348b32cc8ed58a972c6fd53b20279549
> Author: Deepak Rawat <drawat@vmware.com>
> AuthorDate: Tue Oct 16 15:23:41 2018 -0700
> Commit: Daniel Vetter <daniel.vetter@ffwll.ch>
> CommitDate: Wed Oct 17 09:41:07 2018 +0200
>
> tests/kms_selftest: Integrate kernel selftest test-drm_modeset
Hm not sure what I looked at, but it wasnt there. Sorry for the noise.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-06-25 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 22:23 [igt-dev] [PATCH i-g-t 1/5] lib/igt_fb: Call dumb_destroy ioctl in case of dumb buffers Deepak Rawat
2018-10-16 22:23 ` [Intel-gfx] [PATCH i-g-t 2/5] lib/igt_fb: Check for cairo surface success Deepak Rawat
2018-10-16 22:23 ` [igt-dev] [PATCH i-g-t 3/5] lib: Don't call igt_require_fb_modifiers() when no modifier Deepak Rawat
2018-10-16 22:23 ` [igt-dev] [PATCH i-g-t 4/5] tests/kms_atomic: Add a new test case for FB_DAMAGE_CLIPS plane property Deepak Rawat
2018-10-16 22:23 ` [igt-dev] [PATCH i-g-t 5/5] tests/kms_selftest: Integrate kernel selftest test-drm_modeset Deepak Rawat
2019-06-20 13:20 ` [igt-dev] [Intel-gfx] " Daniel Vetter
2019-06-25 6:01 ` Arkadiusz Hiler
2019-06-25 15:37 ` Daniel Vetter [this message]
2019-07-03 10:37 ` Daniel Vetter
2019-07-03 10:53 ` Arkadiusz Hiler
2018-10-17 0:09 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] lib/igt_fb: Call dumb_destroy ioctl in case of dumb buffers Patchwork
2018-10-17 2:26 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20190625153701.GA12905@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=arkadiusz.hiler@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=petri.latvala@intel.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