From: Jani Nikula <jani.nikula@intel.com>
To: Maxime Ripard <mripard@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Simona Vetter <simona.vetter@ffwll.ch>,
David Airlie <airlied@gmail.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/doc: Document KUnit expectations
Date: Mon, 13 Jan 2025 12:50:26 +0200 [thread overview]
Message-ID: <87v7ujhtsd.fsf@intel.com> (raw)
In-Reply-To: <20250113101100.1373856-1-mripard@kernel.org>
On Mon, 13 Jan 2025, Maxime Ripard <mripard@kernel.org> wrote:
> 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 fair.
Acked-by: Jani Nikula <jani.nikula@intel.com>
---
On a related note, I was recently pinged again about the framebuffer
kunit tests causing warning backtraces on successful runs. I don't know
what to tell people, we kind of ended at an impasse [1]. Most tests
don't emit warnings, some do, and I'm still as reluctant as ever to
recommend folks to ignore warnings when running tests. We can agree to
disagree, but it doesn't really move things forward.
BR,
Jani.
[1] https://lore.kernel.org/r/cover.1726594684.git.jani.nikula@intel.com
>
> ---
>
> I'm not too sure where those guidelines should be placed. Is it the best
> place?
> ---
> Documentation/gpu/drm-internals.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/gpu/drm-internals.rst b/Documentation/gpu/drm-internals.rst
> index cb9ae282771c..94f93fd3b8a0 100644
> --- a/Documentation/gpu/drm-internals.rst
> +++ b/Documentation/gpu/drm-internals.rst
> @@ -206,10 +206,17 @@ follows:
> The configuration included in ``.kunitconfig`` should be as generic as
> possible.
> ``CONFIG_VIRTIO_UML`` and ``CONFIG_UML_PCI_OVER_VIRTIO`` are not
> included in it because they are only required for User Mode Linux.
>
> +KUnit Coverage Rules
> +~~~~~~~~~~~~~~~~~~~~
> +
> +KUnit support is gradually added to the DRM framework and helpers. There's no
> +general requirement for the framework and helpers to have KUnit tests at the
> +moment. However, patches that are affecting a function or helper already
> +covered by KUnit tests must provide tests if the change calls for one.
>
> Legacy Support Code
> ===================
>
> The section very briefly covers some of the old legacy support code
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-01-13 10:50 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 [this message]
2025-02-19 9:06 ` Javier Martinez Canillas
2025-02-19 13:24 ` Simona Vetter
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=87v7ujhtsd.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona.vetter@ffwll.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.