From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/5] dt-bindings: drm/bridge Document Cadence MHDP DPI/DP bridge bindings
Date: Tue, 28 Aug 2018 19:28:19 -0500 [thread overview]
Message-ID: <20180829002819.GA12330@bogus> (raw)
In-Reply-To: <1535451894-2518-5-git-send-email-dkos@cadence.com>
On Tue, 28 Aug 2018 11:24:47 +0100, Damian Kos wrote:
> From: Quentin Schulz <quentin.schulz@bootlin.com>
>
> Signed-off-by: Damian Kos <dkos@cadence.com>
> ---
> .../bindings/display/bridge/cdns,mhdp.txt | 43 +++++++++++++++++++
> 1 file changed, 43 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/display/bridge/cdns,mhdp.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-08-29 0:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 10:24 [PATCH v3 0/5] drm: add support for Cadence MHDP DPI/DP bridge Damian Kos
2018-08-28 10:24 ` [PATCH v3 1/5] drm/rockchip: prepare common code for cdns and rk dpi/dp driver Damian Kos
2018-09-13 10:00 ` Andrzej Hajda
2018-09-13 10:15 ` Damian Kos
2018-08-28 10:24 ` [PATCH v3 2/5] drm/dp: fix link probing for devices supporting DP 1.4+ Damian Kos
2018-09-13 11:08 ` Andrzej Hajda
2018-08-28 10:24 ` [PATCH v3 3/5] drm/dp: make dp_link_status and dp_get_lane_status usable from outside of the core Damian Kos
2018-09-13 11:20 ` Andrzej Hajda
2018-08-28 10:24 ` [PATCH v3 4/5] dt-bindings: drm/bridge Document Cadence MHDP DPI/DP bridge bindings Damian Kos
2018-08-29 0:28 ` Rob Herring [this message]
2018-09-13 11:23 ` Andrzej Hajda
2018-08-28 10:24 ` [PATCH v3 5/5] drm/bridge: add preliminary driver for cadence dpi/dp bridge Damian Kos
2018-09-13 12:30 ` Heiko Stuebner
2018-09-13 12:31 ` [PATCH v3 0/5] drm: add support for Cadence MHDP DPI/DP bridge Heiko Stuebner
2018-09-18 13:18 ` 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=20180829002819.GA12330@bogus \
--to=robh@kernel.org \
--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