From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/6] drm: add support for Cadence MHDP DPI/DP bridge.
Date: Mon, 05 Nov 2018 12:30:05 +0200 [thread overview]
Message-ID: <3056496.a8qoricJmv@avalon> (raw)
In-Reply-To: <CY1PR0701MB166434BBB71DB76593E0F513CDCA0@CY1PR0701MB1664.namprd07.prod.outlook.com>
Hi Damian,
On Monday, 5 November 2018 11:44:53 EET Damian Kos wrote:
> Hi Guys,
>
> I'm wondering if this time patch is so good that there're no change
> requests, or is it so bad that it was rejected without a comment : )
> Please let me know if this patch is being in review or was rejected and, if
> so, what needs to be changed.
I unfortunately don't have time to review your series for the time being.
Hopefully someone else will have a better review bandwidth :-) Sorry about
that.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-11-05 10:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 21:42 [PATCH v6 0/6] drm: add support for Cadence MHDP DPI/DP bridge Damian Kos
2018-10-08 21:42 ` [PATCH v6 1/6] drm/rockchip: prepare common code for cdns and rk dpi/dp driver Damian Kos
2018-10-08 21:42 ` [PATCH v6 2/6] drm/dp: fix link probing for devices supporting DP 1.4+ Damian Kos
2018-10-08 21:42 ` [PATCH v6 3/6] dt-bindings: drm/bridge: Document Cadence MHDP bridge bindings Damian Kos
2018-10-08 21:42 ` [PATCH v6 4/6] drm: bridge: add support for Cadence MHDP DPI/DP bridge Damian Kos
2018-11-05 13:10 ` Andrzej Hajda
2018-10-08 21:42 ` [PATCH v6 5/6] drm/bridge: add support for MST in mhdp8546 driver Damian Kos
2018-11-07 11:40 ` Andrzej Hajda
2018-11-08 14:53 ` Damian Kos
2018-10-08 21:42 ` [PATCH v6 6/6] drm/bridge: add PHY initialization " Damian Kos
2018-11-07 11:49 ` Andrzej Hajda
2018-11-05 9:44 ` [PATCH v6 0/6] drm: add support for Cadence MHDP DPI/DP bridge Damian Kos
2018-11-05 10:30 ` Laurent Pinchart [this message]
2018-11-05 10:33 ` Damian Kos
2018-11-05 11:09 ` Andrzej Hajda
2018-11-05 11:34 ` Damian Kos
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=3056496.a8qoricJmv@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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