From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jyri Sarha <jsarha@ti.com>
Cc: Liviu.Dudau@arm.com, dri-devel@lists.freedesktop.org,
tomi.valkeinen@ti.com
Subject: Re: [PATCH RFC 1/6] drm: drm_color_mgmt.h needs struct drm_crtc declaration
Date: Fri, 21 Apr 2017 14:46:07 +0300 [thread overview]
Message-ID: <2449963.1HSbn6RA2x@avalon> (raw)
In-Reply-To: <69c913b3ae3fc7235c059e08f58fb0a172d98cf8.1492768073.git.jsarha@ti.com>
Hi Jyri,
Thank you for the patch
On Friday 21 Apr 2017 12:51:12 Jyri Sarha wrote:
No commit message ?
> Signed-off-by: Jyri Sarha <jsarha@ti.com>
Apart from that,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> include/drm/drm_color_mgmt.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/drm/drm_color_mgmt.h b/include/drm/drm_color_mgmt.h
> index bce4a53..03a59cb 100644
> --- a/include/drm/drm_color_mgmt.h
> +++ b/include/drm/drm_color_mgmt.h
> @@ -25,6 +25,8 @@
>
> #include <linux/ctype.h>
>
> +struct drm_crtc;
> +
> uint32_t drm_color_lut_extract(uint32_t user_input, uint32_t
> bit_precision);
>
> void drm_crtc_enable_color_mgmt(struct drm_crtc *crtc,
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-21 11:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 9:51 [PATCH RFC 0/6] drm: Add properties to control YCbCr to RGB conversion Jyri Sarha
2017-04-21 9:51 ` [PATCH RFC 1/6] drm: drm_color_mgmt.h needs struct drm_crtc declaration Jyri Sarha
2017-04-21 11:46 ` Laurent Pinchart [this message]
2017-04-21 9:51 ` [PATCH RFC 2/6] drm: Make drm_atomic_replace_property_blob_from_id() more generic Jyri Sarha
2017-04-21 11:47 ` Laurent Pinchart
2017-05-02 8:31 ` Daniel Vetter
2017-04-21 9:51 ` [PATCH RFC 3/6] drm: Plane YCbCr to RGB conversion related properties Jyri Sarha
2017-04-21 11:17 ` Ville Syrjälä
2017-04-21 12:10 ` Laurent Pinchart
2017-04-21 13:08 ` Ville Syrjälä
2017-04-21 12:58 ` Sharma, Shashank
2017-04-21 13:39 ` Jyri Sarha
2017-04-21 13:52 ` Ville Syrjälä
2017-04-21 14:53 ` Brian Starkey
2017-04-21 15:21 ` Ville Syrjälä
2017-04-21 15:34 ` Brian Starkey
2017-04-21 16:49 ` Ville Syrjälä
2017-04-24 12:58 ` Brian Starkey
2017-04-24 9:02 ` [PATCH] RFC: Design: DRM: Blending pipeline using DRM plane properties Shashank Sharma
2017-04-24 13:21 ` [PATCH RFC 3/6] drm: Plane YCbCr to RGB conversion related properties Jyri Sarha
2017-04-24 15:13 ` Ville Syrjälä
2017-04-24 15:49 ` Jyri Sarha
2017-04-24 16:55 ` Ville Syrjälä
2017-04-26 12:56 ` Jyri Sarha
2017-04-26 13:28 ` Sharma, Shashank
2017-04-26 17:22 ` Ville Syrjälä
2017-05-02 8:33 ` Daniel Vetter
2017-05-02 9:29 ` Jyri Sarha
2017-04-21 9:51 ` [PATCH RFC 4/6] drm/omap: cleanup color space conversion Jyri Sarha
2017-04-21 11:53 ` Laurent Pinchart
2017-04-21 9:51 ` [PATCH RFC 5/6] drm/omap: csc full range support Jyri Sarha
2017-04-21 11:55 ` Laurent Pinchart
2017-04-21 9:51 ` [PATCH RFC 6/6] drm/omap: Enable ycbcr_to_rgb_properties for omapdrm planes REVISIT Jyri Sarha
2017-04-21 12:53 ` [PATCH RFC 0/6] drm: Add properties to control YCbCr to RGB conversion Sharma, Shashank
2017-04-21 13:50 ` Liviu Dudau
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=2449963.1HSbn6RA2x@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=Liviu.Dudau@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=tomi.valkeinen@ti.com \
/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