From: Maxime Ripard <maxime@cerno.tech>
To: David Airlie <airlied@linux.ie>,
Maxime Ripard <maxime@cerno.tech>,
Maxime Ripard <mripard@kernel.org>, Emma Anholt <emma@anholt.net>,
Eric Anholt <eric@anholt.net>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Joerg Quinten <aBUGSworstnightmare@gmail.com>,
dri-devel@lists.freedesktop.org,
Chris Morgan <macromorgan@hotmail.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>
Subject: Re: [PATCH v3 0/7] drm/vc4: dpi: Various improvements
Date: Thu, 1 Dec 2022 11:18:11 +0100 [thread overview]
Message-ID: <166988985776.410916.3768232487459584873.b4-ty@cerno.tech> (raw)
In-Reply-To: <20221013-rpi-dpi-improvements-v3-0-eb76e26a772d@cerno.tech>
On Thu, 01 Dec 2022 09:42:45 +0100, Maxime Ripard wrote:
> Those patches have been in the downstream RaspberryPi tree for a while and help
> to support more DPI displays.
>
> Let me know what you think,
> Maxime
>
>
> [...]
Applied to drm/drm-misc (drm-misc-next).
Thanks!
Maxime
prev parent reply other threads:[~2022-12-01 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 8:42 [PATCH v3 0/7] drm/vc4: dpi: Various improvements Maxime Ripard
2022-12-01 8:42 ` [PATCH v3 1/7] media: uapi: add MEDIA_BUS_FMT_RGB565_1X24_CPADHI Maxime Ripard
2022-12-01 8:42 ` [PATCH v3 2/7] media: uapi: add MEDIA_BUS_FMT_BGR666_1X18 Maxime Ripard
2022-12-01 8:42 ` [PATCH v3 3/7] media: uapi: add MEDIA_BUS_FMT_BGR666_1X24_CPADHI Maxime Ripard
2022-12-01 9:56 ` Laurent Pinchart
2022-12-01 8:42 ` [PATCH v3 4/7] drm/vc4: dpi: Support RGB565 format Maxime Ripard
2022-12-01 8:42 ` [PATCH v3 5/7] drm/vc4: dpi: Support BGR666 formats Maxime Ripard
2022-12-01 8:42 ` [PATCH v3 6/7] drm/vc4: dpi: Change the default DPI format to being 18bpp, not 24 Maxime Ripard
2022-12-01 8:42 ` [PATCH v3 7/7] drm/vc4: dpi: Fix format mapping for RGB565 Maxime Ripard
2022-12-01 10:18 ` Maxime Ripard [this message]
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=166988985776.410916.3768232487459584873.b4-ty@cerno.tech \
--to=maxime@cerno.tech \
--cc=aBUGSworstnightmare@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=eric@anholt.net \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macromorgan@hotmail.com \
--cc=mripard@kernel.org \
--cc=robh@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 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).