From: Simona Vetter <simona.vetter@ffwll.ch>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: Maxime Ripard <mripard@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Simona Vetter <simona.vetter@ffwll.ch>,
David Airlie <airlied@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH] drm/doc: Document KUnit expectations
Date: Wed, 19 Feb 2025 14:24:59 +0100 [thread overview]
Message-ID: <Z7Xbq-P0RTttJfz-@phenom.ffwll.local> (raw)
In-Reply-To: <87v7t6paks.fsf@minerva.mail-host-address-is-not-set>
On Wed, Feb 19, 2025 at 10:06:59AM +0100, Javier Martinez Canillas wrote:
> Maxime Ripard <mripard@kernel.org> writes:
>
> > The DRM and KMS frameworks and helpers gain more and more kunit
> > coverage, so let's document what our expectations are.
> >
> > Suggested-by: Jani Nikula <jani.nikula@intel.com>
> > Signed-off-by: Maxime Ripard <mripard@kernel.org>
> >
> > ---
> >
>
> Seems a reasonable expection to me.
>
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Acked-by: Simona Vetter <simona.vetter@ffwll.ch>
I think some more acks from folks working on Kunit tests would be great,
but that aside I think this accurately summarizes the discussion we had a
while back.
-Sima
--
Simona Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2025-02-19 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 10:11 [PATCH] drm/doc: Document KUnit expectations Maxime Ripard
2025-01-13 10:50 ` Jani Nikula
2025-02-19 9:06 ` Javier Martinez Canillas
2025-02-19 13:24 ` Simona Vetter [this message]
2025-02-26 12:53 ` Tvrtko Ursulin
2025-02-26 14:52 ` Maíra Canal
2025-02-26 15:34 ` 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=Z7Xbq-P0RTttJfz-@phenom.ffwll.local \
--to=simona.vetter@ffwll.ch \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=javierm@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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