All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Nicolas Frattaroli" <nicolas.frattaroli@collabora.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/tests: Move test EDID data to separate .c file
Date: Wed, 10 Jun 2026 14:40:59 +0000	[thread overview]
Message-ID: <20260610144100.659E71F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260610-test-edid-array-definition-fix-v2-1-9de4605c4869@collabora.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly added drm_kunit_edid.c file is built as a loadable module but lacks a MODULE_LICENSE() declaration.
--

commit 6969a389dfc7ebf286991ec9afae031d0abd753f
Author: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>

drm/tests: Move test EDID data to separate .c file

This commit moves the test EDID array definitions from a header file into a newly created drm_kunit_edid.c file. The arrays are exported so they can be shared among different KUnit tests without duplicating data across multiple users.

Link: https://lore.kernel.org/r/04ff70850213ae0f75486b1a27a7edb6fb4e71c3@intel.com/

> diff --git a/drivers/gpu/drm/tests/Makefile b/drivers/gpu/drm/tests/Makefile
> index 3b83e6616fb25..e7193b49cf91f 100644
> --- a/drivers/gpu/drm/tests/Makefile
> +++ b/drivers/gpu/drm/tests/Makefile
> @@ -24,6 +24,7 @@ obj-$(CONFIG_DRM_KUNIT_TEST) += \
>  	drm_probe_helper_test.o \
>  	drm_rect_test.o \
>  	drm_sysfb_modeset_test.o \
> -	drm_fixp_test.o
> +	drm_fixp_test.o \
> +	drm_kunit_edid.o

[ ... ]

> diff --git a/drivers/gpu/drm/tests/drm_kunit_edid.c b/drivers/gpu/drm/tests/drm_kunit_edid.c
> new file mode 100644
> index 0000000000000..0976372860627
> --- /dev/null
> +++ b/drivers/gpu/drm/tests/drm_kunit_edid.c
> @@ -0,0 +1,991 @@
> +// SPDX-License-Identifier: GPL-2.0
> +
> +#include <linux/export.h>
> +
> +#include "drm_kunit_edid.h"

[Severity: Low]
Because drm_kunit_edid.o is added directly to obj-$(CONFIG_DRM_KUNIT_TEST) in
the Makefile, it will be built as a standalone module when that config is set
to 'm'. Does this new file need to include <linux/module.h> and provide a
MODULE_LICENSE() declaration to prevent modpost warnings and a tainted kernel
when loaded?

> +
> +/*
> + * edid-decode (hex):
> + *
> + * 00 ff ff ff ff ff ff 00 31 d8 2a 00 00 00 00 00

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260610-test-edid-array-definition-fix-v2-1-9de4605c4869@collabora.com?part=1

  reply	other threads:[~2026-06-10 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 14:31 [PATCH v2] drm/tests: Move test EDID data to separate .c file Nicolas Frattaroli
2026-06-10 14:40 ` sashiko-bot [this message]
2026-06-11  7:35 ` 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=20260610144100.659E71F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=nicolas.frattaroli@collabora.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.