From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 05/19] drm/vc4: Use the alpha format field in drm_format_info
Date: Tue, 23 Jan 2018 07:35:10 +1100 [thread overview]
Message-ID: <87vaft7htt.fsf@anholt.net> (raw)
In-Reply-To: <38d4d0a085634a0b8308e819c846b9173d4d93df.1516617243.git-series.maxime.ripard@free-electrons.com>
Maxime Ripard <maxime.ripard@free-electrons.com> writes:
> Now that the drm_format_info has a alpha field to tell if a format embeds
> an alpha component in it, let's use it.
>
> Cc: Eric Anholt <eric@anholt.net>
> Reviewed-by: Daniel Vetter <daniel.vetter@intel.com>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
I had sent my r-b for the last version of this.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180123/e660b02d/attachment.sig>
next prev parent reply other threads:[~2018-01-22 20:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 10:35 [PATCH v2 00/19] drm/sun4i: Support more planes, zpos and plane-wide alpha Maxime Ripard
2018-01-22 10:35 ` [PATCH v2 01/19] drm/fourcc: Add a alpha field to drm_format_info Maxime Ripard
2018-01-22 10:35 ` [PATCH v2 02/19] drm/atmel-hlcdc: Use the alpha format field in drm_format_info Maxime Ripard
2018-01-22 10:35 ` [PATCH v2 03/19] drm/atmel-exynos: " Maxime Ripard
2018-01-22 10:35 ` [PATCH v2 04/19] drm/rockchip: " Maxime Ripard
2018-01-22 10:35 ` [PATCH v2 05/19] drm/vc4: " Maxime Ripard
2018-01-22 20:35 ` Eric Anholt [this message]
2018-01-29 13:06 ` Maxime Ripard
2018-01-22 10:35 ` [PATCH v2 06/19] drm/blend: Add a generic alpha property Maxime Ripard
2018-01-22 10:35 ` [PATCH v2 07/19] drm/atmel-hclcdc: Convert to the new " Maxime Ripard
2018-01-22 10:35 ` [PATCH v2 08/19] drm/rcar-du: " Maxime Ripard
2018-01-22 10:35 ` [PATCH v2 09/19] drm/sun4i: backend: Fix structure indentation Maxime Ripard
2018-01-29 1:51 ` Chen-Yu Tsai
2018-01-22 10:35 ` [PATCH v2 10/19] drm/sun4i: backend: Fix define typo Maxime Ripard
2018-01-29 1:52 ` Chen-Yu Tsai
2018-01-22 10:35 ` [PATCH v2 11/19] drm/sun4i: framebuffer: Add a custom atomic_check Maxime Ripard
2018-01-29 1:52 ` Chen-Yu Tsai
2018-01-22 10:35 ` [PATCH v2 12/19] drm/sun4i: backend: Move the coord function in the shared part Maxime Ripard
2018-01-29 1:52 ` Chen-Yu Tsai
2018-01-22 10:35 ` [PATCH v2 13/19] drm/sun4i: backend: Set a default zpos in our reset hook Maxime Ripard
2018-01-29 1:53 ` Chen-Yu Tsai
2018-01-22 10:35 ` [PATCH v2 14/19] drm/sun4i: backend: Add support for zpos Maxime Ripard
2018-01-29 2:01 ` Chen-Yu Tsai
2018-01-22 10:35 ` [PATCH v2 15/19] drm/sun4i: backend: Check for the number of alpha planes Maxime Ripard
2018-01-29 2:14 ` Chen-Yu Tsai
2018-01-22 10:35 ` [PATCH v2 16/19] drm/sun4i: backend: Assign the pipes automatically Maxime Ripard
2018-01-29 2:22 ` Chen-Yu Tsai
2018-01-29 13:08 ` Maxime Ripard
2018-01-22 10:35 ` [PATCH v2 17/19] drm/sun4i: backend: Make zpos configurable Maxime Ripard
2018-01-29 2:23 ` Chen-Yu Tsai
2018-01-22 10:35 ` [PATCH v2 18/19] drm/sun4i: Add support for plane alpha Maxime Ripard
2018-01-22 10:35 ` [PATCH v2 19/19] drm/sun4i: backend: Remove ARGB spoofing 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=87vaft7htt.fsf@anholt.net \
--to=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.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 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).