From: "José Expósito" <jose.exposito89@gmail.com>
To: louis.chauvet@bootlin.com
Cc: airlied@gmail.com, arthurgrillo@riseup.net, corbet@lwn.net,
dri-devel@lists.freedesktop.org, hamohammed.sa@gmail.com,
jeremie.dautheribes@bootlin.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com,
mairacanal@riseup.net, marcheu@google.com, melissa.srw@gmail.com,
miquel.raynal@bootlin.com, mripard@kernel.org,
nicolejadeyee@google.com, pekka.paalanen@haloniitty.fi,
rdunlap@infradead.org, rodrigosiqueiramelo@gmail.com,
seanpaul@google.com, simona.vetter@ffwll.ch, simona@ffwll.ch,
thomas.petazzoni@bootlin.com, tzimmermann@suse.de,
"José Expósito" <jose.exposito89@gmail.com>
Subject: [PATCH v16 4/7] drm: Export symbols to use in tests
Date: Fri, 31 Jan 2025 09:40:55 +0100 [thread overview]
Message-ID: <20250131084056.2889-1-jose.exposito89@gmail.com> (raw)
In-Reply-To: <20250121-yuv-v16-4-a61f95a99432@bootlin.com>
> The functions drm_get_color_encoding_name and drm_get_color_range_name
> are useful for clarifying test results. Therefore, export them so they
> can be used in tests built as modules.
>
> Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>
Nice and simple, in the next version:
Reviewed-by: José Expósito <jose.exposito89@gmail.com>
> ---
> drivers/gpu/drm/drm_color_mgmt.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_color_mgmt.c b/drivers/gpu/drm/drm_color_mgmt.c
> index 3969dc548cff605cbdd3d56dceafb2ca00a5c886..b73a998352d175a26c69e0878da28a6288cfc8b7 100644
> --- a/drivers/gpu/drm/drm_color_mgmt.c
> +++ b/drivers/gpu/drm/drm_color_mgmt.c
> @@ -28,6 +28,7 @@
> #include <drm/drm_device.h>
> #include <drm/drm_drv.h>
> #include <drm/drm_print.h>
> +#include <kunit/visibility.h>
>
> #include "drm_crtc_internal.h"
>
> @@ -494,6 +495,7 @@ const char *drm_get_color_encoding_name(enum drm_color_encoding encoding)
>
> return color_encoding_name[encoding];
> }
> +EXPORT_SYMBOL_IF_KUNIT(drm_get_color_encoding_name);
>
> /**
> * drm_get_color_range_name - return a string for color range
> @@ -509,6 +511,7 @@ const char *drm_get_color_range_name(enum drm_color_range range)
>
> return color_range_name[range];
> }
> +EXPORT_SYMBOL_IF_KUNIT(drm_get_color_range_name);
>
> /**
> * drm_plane_create_color_properties - color encoding related plane properties
>
next prev parent reply other threads:[~2025-01-31 8:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 10:48 [PATCH v16 0/7] drm/vkms: Add support for YUV and DRM_FORMAT_R* Louis Chauvet
2025-01-21 10:48 ` [PATCH v16 1/7] drm/vkms: Add YUV support Louis Chauvet
2025-01-21 10:48 ` [PATCH v16 2/7] drm/vkms: Add range and encoding properties to the plane Louis Chauvet
2025-01-21 10:48 ` [PATCH v16 3/7] drm/vkms: Drop YUV formats TODO Louis Chauvet
2025-01-31 8:40 ` José Expósito
2025-01-31 13:02 ` Louis Chauvet
2025-01-31 16:53 ` José Expósito
2025-01-21 10:48 ` [PATCH v16 4/7] drm: Export symbols to use in tests Louis Chauvet
2025-01-31 8:40 ` José Expósito [this message]
2025-01-21 10:48 ` [PATCH v16 5/7] drm/vkms: Create KUnit tests for YUV conversions Louis Chauvet
2025-01-26 17:06 ` Maxime Ripard
2025-01-27 10:48 ` Louis Chauvet
2025-02-05 8:55 ` Maxime Ripard
2025-02-05 15:32 ` Louis Chauvet
2025-02-19 10:15 ` Maxime Ripard
2025-02-19 13:35 ` Louis Chauvet
2025-03-07 10:20 ` Maxime Ripard
2025-03-07 14:50 ` Louis Chauvet
2025-03-10 9:12 ` Pekka Paalanen
2025-03-13 14:29 ` Maxime Ripard
2025-01-31 8:41 ` José Expósito
2025-01-31 13:02 ` Louis Chauvet
2025-01-31 16:57 ` José Expósito
2025-01-21 10:48 ` [PATCH v16 6/7] drm/vkms: Add how to run the Kunit tests Louis Chauvet
2025-01-31 8:41 ` José Expósito
2025-01-21 10:48 ` [PATCH v16 7/7] drm/vkms: Add support for DRM_FORMAT_R* Louis Chauvet
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=20250131084056.2889-1-jose.exposito89@gmail.com \
--to=jose.exposito89@gmail.com \
--cc=airlied@gmail.com \
--cc=arthurgrillo@riseup.net \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=jeremie.dautheribes@bootlin.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mairacanal@riseup.net \
--cc=marcheu@google.com \
--cc=melissa.srw@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=mripard@kernel.org \
--cc=nicolejadeyee@google.com \
--cc=pekka.paalanen@haloniitty.fi \
--cc=rdunlap@infradead.org \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=seanpaul@google.com \
--cc=simona.vetter@ffwll.ch \
--cc=simona@ffwll.ch \
--cc=thomas.petazzoni@bootlin.com \
--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