mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: "André Almeida" <andrealmeid@collabora.com>
Cc: Daniel Vetter <daniel@ffwll.ch>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Brendan Higgins <brendanhiggins@google.com>,
	Daniel Latypov <dlatypov@google.com>,
	David Gow <davidgow@google.com>,
	kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
	dri-devel@lists.freedesktop.org, daniel@fooishbar.org,
	igt-dev@lists.freedesktop.org, leandro.ribeiro@collabora.com,
	n@nfraprado.net, rodrigosiqueiramelo@gmail.com,
	melissa.srw@gmail.com, ~lkcamp/discussion@lists.sr.ht,
	isabbasso@riseup.net, maira.canal@usp.br, arthur.grillo@usp.br,
	linux-kernel@vger.kernel.org
Subject: Re: [igt-dev] [RFC PATCH 0/1] drm: selftest: Convert to KUnit
Date: Thu, 11 Nov 2021 15:19:57 +0200	[thread overview]
Message-ID: <YY0YfV4WECXFMhYw@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20211111003453.209115-1-andrealmeid@collabora.com>

On Wed, Nov 10, 2021 at 09:34:52PM -0300, André Almeida wrote:
> Hi,
> 
> This RFC is a preview of the progress we made in the KUnit hackathon[0].
> This patch, made by Maíra and Arthur, converts the damage helper test
> from the original DRM selftest framework to use the KUnit framework.
> 
> [0] https://groups.google.com/g/kunit-dev/c/YqFR1q2uZvk/m/IbvItSfHBAAJ
> 
> The IGT part of this work can be found here:
> https://gitlab.freedesktop.org/isinyaaa/igt-gpu-tools/-/tree/introduce-kunit

IGT side approach looks good. There's a couple of obscure bugs that I
spotted but nothing that is unfixable when it's time to review in
detail.


-- 
Petri Latvala

      parent reply	other threads:[~2021-11-11 13:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  0:34 André Almeida
2021-11-11  0:34 ` [RFC PATCH 1/1] drm: selftest: convert drm_damage_helper selftest " André Almeida
2021-11-11  2:11   ` Daniel Latypov
2021-11-11 13:19 ` Petri Latvala [this message]

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=YY0YfV4WECXFMhYw@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=andrealmeid@collabora.com \
    --cc=arthur.grillo@usp.br \
    --cc=brendanhiggins@google.com \
    --cc=daniel@ffwll.ch \
    --cc=daniel@fooishbar.org \
    --cc=davidgow@google.com \
    --cc=dlatypov@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=isabbasso@riseup.net \
    --cc=kunit-dev@googlegroups.com \
    --cc=leandro.ribeiro@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=maira.canal@usp.br \
    --cc=melissa.srw@gmail.com \
    --cc=n@nfraprado.net \
    --cc=rodrigosiqueiramelo@gmail.com \
    --cc=skhan@linuxfoundation.org \
    --cc=~lkcamp/discussion@lists.sr.ht \
    /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

all inboxes | Powered by JetHome®