linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Louis Chauvet <louis.chauvet@bootlin.com>
To: "Melissa Wen" <melissa.srw@gmail.com>,
	"Maíra Canal" <mairacanal@riseup.net>,
	"Haneen Mohammed" <hamohammed.sa@gmail.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	rdunlap@infradead.org, arthurgrillo@riseup.net,
	"Jonathan Corbet" <corbet@lwn.net>,
	pekka.paalanen@haloniitty.fi, "Simona Vetter" <simona@ffwll.ch>,
	"Rodrigo Siqueira" <siqueira@igalia.com>,
	"Simona Vetter" <simona.vetter@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	jeremie.dautheribes@bootlin.com, miquel.raynal@bootlin.com,
	thomas.petazzoni@bootlin.com, seanpaul@google.com,
	marcheu@google.com, nicolejadeyee@google.com,
	linux-doc@vger.kernel.org,
	"Louis Chauvet" <louis.chauvet@bootlin.com>,
	"José Expósito" <jose.exposito89@gmail.com>
Subject: [PATCH v18 5/8] drm: Export symbols to use in tests
Date: Tue, 15 Apr 2025 15:55:36 +0200	[thread overview]
Message-ID: <20250415-yuv-v18-5-f2918f71ec4b@bootlin.com> (raw)
In-Reply-To: <20250415-yuv-v18-0-f2918f71ec4b@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.

Reviewed-by: José Expósito <jose.exposito89@gmail.com>
Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.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 3969dc548cff..b73a998352d1 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

-- 
2.49.0


  parent reply	other threads:[~2025-04-15 13:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 13:55 [PATCH v18 0/8] drm/vkms: Add support for YUV and DRM_FORMAT_R* Louis Chauvet
2025-04-15 13:55 ` [PATCH v18 1/8] drm/vkms: Document pixel_argb_u16 Louis Chauvet
2025-04-17  8:38   ` Pekka Paalanen
2025-04-17 11:17   ` Pekka Paalanen
2025-04-15 13:55 ` [PATCH v18 2/8] drm/vkms: Add YUV support Louis Chauvet
2025-04-15 13:55 ` [PATCH v18 3/8] drm/vkms: Add range and encoding properties to the plane Louis Chauvet
2025-04-15 13:55 ` [PATCH v18 4/8] drm/vkms: Drop YUV formats TODO Louis Chauvet
2025-04-15 13:55 ` Louis Chauvet [this message]
2025-04-15 13:55 ` [PATCH v18 6/8] drm/vkms: Create KUnit tests for YUV conversions Louis Chauvet
2025-05-12 13:07   ` Louis Chauvet
2025-05-22 15:39     ` Maxime Ripard
2025-05-27 13:36       ` Louis Chauvet
2025-05-27 15:57         ` Maxime Ripard
2025-04-15 13:55 ` [PATCH v18 7/8] drm/vkms: Add how to run the Kunit tests Louis Chauvet
2025-04-15 13:55 ` [PATCH v18 8/8] drm/vkms: Add support for DRM_FORMAT_R* Louis Chauvet
2025-05-28 14:20 ` [PATCH v18 0/8] drm/vkms: Add support for YUV and 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=20250415-yuv-v18-5-f2918f71ec4b@bootlin.com \
    --to=louis.chauvet@bootlin.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=jose.exposito89@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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=seanpaul@google.com \
    --cc=simona.vetter@ffwll.ch \
    --cc=simona@ffwll.ch \
    --cc=siqueira@igalia.com \
    --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;
as well as URLs for NNTP newsgroup(s).