All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuan Can <yuancan@huawei.com>
To: <tomba@kernel.org>, <airlied@gmail.com>, <daniel@ffwll.ch>,
	<neil.armstrong@linaro.org>, <bparrot@ti.com>,
	<cai.huoqing@linux.dev>, <arnd@arndb.de>, <guozhengkui@vivo.com>,
	<jsarha@ti.com>, <laurent.pinchart@ideasonboard.com>,
	<dri-devel@lists.freedesktop.org>
Cc: yuancan@huawei.com
Subject: [PATCH v2] drm/omapdrm: Remove unused struct csc_coef_rgb2yuv
Date: Fri, 14 Oct 2022 02:48:10 +0000	[thread overview]
Message-ID: <20221014024810.21675-1-yuancan@huawei.com> (raw)

After commit 64ff18911878, struct csc_coef_rgb2yuv is not used any more
and can be removed as well.

Fixes: 64ff18911878 ("drm/omap: Enable COLOR_ENCODING and COLOR_RANGE properties for planes")
Signed-off-by: Yuan Can <yuancan@huawei.com>
---
changes in v2:
- adjust commit msg
---
 drivers/gpu/drm/omapdrm/dss/dispc.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/drivers/gpu/drm/omapdrm/dss/dispc.c b/drivers/gpu/drm/omapdrm/dss/dispc.c
index 0ee344ebcd1c..aacad5045e95 100644
--- a/drivers/gpu/drm/omapdrm/dss/dispc.c
+++ b/drivers/gpu/drm/omapdrm/dss/dispc.c
@@ -855,11 +855,6 @@ struct csc_coef_yuv2rgb {
 	bool full_range;
 };
 
-struct csc_coef_rgb2yuv {
-	int yr, yg, yb, cbr, cbg, cbb, crr, crg, crb;
-	bool full_range;
-};
-
 static void dispc_ovl_write_color_conv_coef(struct dispc_device *dispc,
 					    enum omap_plane_id plane,
 					    const struct csc_coef_yuv2rgb *ct)
-- 
2.17.1


             reply	other threads:[~2022-10-14  2:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  2:48 Yuan Can [this message]
2022-10-15 17:52 ` [PATCH v2] drm/omapdrm: Remove unused struct csc_coef_rgb2yuv Laurent Pinchart
2022-12-16  8:26 ` Tomi Valkeinen

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=20221014024810.21675-1-yuancan@huawei.com \
    --to=yuancan@huawei.com \
    --cc=airlied@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bparrot@ti.com \
    --cc=cai.huoqing@linux.dev \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guozhengkui@vivo.com \
    --cc=jsarha@ti.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=neil.armstrong@linaro.org \
    --cc=tomba@kernel.org \
    /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.