From: "Maxime Ripard" <mripard@kernel.org>
To: "Jocelyn Falempe" <jfalempe@redhat.com>
Cc: tzimmermann@suse.de, javierm@redhat.com,
dri-devel@lists.freedesktop.org, ppaalanen@gmail.com,
mripard@kernel.org, airlied@redhat.com
Subject: Re: [PATCH v3] drm/plane: Add documentation about software color conversion.
Date: Fri, 25 Aug 2023 14:14:29 +0000 [thread overview]
Message-ID: <4f8eda60484ec9dc41c2200ac936ea63.mripard@kernel.org> (raw)
In-Reply-To: <20230825140434.182664-1-jfalempe@redhat.com>
On Fri, 25 Aug 2023 16:04:18 +0200, Jocelyn Falempe wrote:
> After discussions on IRC, the consensus is that the DRM drivers should
> avoid software color conversion, and only advertise the formats supported
> by hardware.
> Update the doc accordingly so that the rule and exceptions are clear for
> everyone.
>
> [ ... ]
Acked-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2023-08-25 14:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 14:04 [PATCH v3] drm/plane: Add documentation about software color conversion Jocelyn Falempe
2023-08-25 14:14 ` Maxime Ripard [this message]
2023-08-25 14:25 ` Javier Martinez Canillas
2023-08-28 7:35 ` Pekka Paalanen
2023-09-08 9:21 ` Thomas Zimmermann
2023-09-08 10:58 ` Maxime Ripard
2023-09-08 13:22 ` Thomas Zimmermann
2023-09-08 13:27 ` Simon Ser
2023-09-08 13:46 ` Javier Martinez Canillas
2023-09-08 14:06 ` Jocelyn Falempe
2023-09-08 14:13 ` Thomas Zimmermann
2023-09-08 14:09 ` Thomas Zimmermann
2023-09-08 11:16 ` Pekka Paalanen
2023-09-08 13:56 ` Thomas Zimmermann
2023-09-08 14:41 ` Pekka Paalanen
2023-09-08 15:10 ` Thomas Zimmermann
2023-09-11 8:38 ` Pekka Paalanen
2023-09-11 10:18 ` Thomas Zimmermann
2023-09-12 15:57 ` Michel Dänzer
2023-09-13 8:14 ` Jocelyn Falempe
2023-09-13 17:02 ` Michel Dänzer
2023-09-08 14:48 ` Jocelyn Falempe
2023-09-08 15:37 ` Thomas Zimmermann
2023-09-11 10:05 ` Jocelyn Falempe
2023-09-11 10:44 ` Thomas Zimmermann
2023-09-11 11:14 ` 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=4f8eda60484ec9dc41c2200ac936ea63.mripard@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=jfalempe@redhat.com \
--cc=ppaalanen@gmail.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 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.