From: Neil Armstrong <narmstrong@baylibre.com>
To: Lubomir Rintel <lkundrak@v3.sk>, Daniel Vetter <daniel@ffwll.ch>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Thierry Reding <thierry.reding@gmail.com>,
Andrzej Hajda <a.hajda@samsung.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v5 0/3] drm: Add support for Chrontel CH7033 VGA/DVI Encoder
Date: Tue, 5 May 2020 09:22:30 +0200 [thread overview]
Message-ID: <07685081-b50e-c4dc-91dd-2ecdbc141660@baylibre.com> (raw)
In-Reply-To: <20200424213539.93157-1-lkundrak@v3.sk>
On 24/04/2020 23:35, Lubomir Rintel wrote:
> Hi,
>
> chained to this message is another spin of a driver for CH7033.
>
> Compared to the previous submission, the integration with device
> component framework and creation of an encoder on component bind has
> been removed. This means that until the Armada driver won't work with
> this driver until it's adjusted to look up the bridges like the other
> drivers do.
>
> Thanks,
> Lubo
>
>
Applying to drm-misc-next
Thanks for your work.
Neil
prev parent reply other threads:[~2020-05-05 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 21:35 [PATCH v5 0/3] drm: Add support for Chrontel CH7033 VGA/DVI Encoder Lubomir Rintel
2020-04-24 21:35 ` [PATCH v5 1/3] dt-bindings: Add vendor prefix for Chrontel, Inc Lubomir Rintel
2020-04-24 21:35 ` [PATCH v5 2/3] dt-bindings: display: Add Chrontel CH7033 Video Encoder binding Lubomir Rintel
2020-04-24 21:35 ` [PATCH v5 3/3] drm/bridge: chrontel-ch7033: Add a new driver Lubomir Rintel
2020-05-04 20:06 ` Sam Ravnborg
2020-05-05 7:21 ` Neil Armstrong
2020-05-05 7:22 ` Neil Armstrong [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=07685081-b50e-c4dc-91dd-2ecdbc141660@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=a.hajda@samsung.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).