From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/9] drm/mediatek: update dt-bindings for mt2712
Date: Wed, 30 May 2018 21:47:46 -0500 [thread overview]
Message-ID: <20180531024746.GA8356@rob-hp-laptop> (raw)
In-Reply-To: <1527489507-24453-2-git-send-email-stu.hsieh@mediatek.com>
On Mon, May 28, 2018 at 02:38:19PM +0800, Stu Hsieh wrote:
> Update device tree binding documentation for the display subsystem for
> Mediatek MT2712 SoCs.
>
> Signed-off-by: Stu Hsieh <stu.hsieh@mediatek.com>
> Acked-by: CK Hu <ck.hu@mediatek.com>
> ---
> Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-05-31 2:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 6:38 [PATCH v4 0/9] Add support for mediatek SOC MT2712 Stu Hsieh
2018-05-28 6:38 ` [PATCH v4 1/9] drm/mediatek: update dt-bindings for mt2712 Stu Hsieh
2018-05-31 2:47 ` Rob Herring [this message]
2018-05-28 6:38 ` [PATCH v4 2/9] drm/mediatek: support maximum 64 mutex mod Stu Hsieh
2018-05-28 6:38 ` [PATCH v4 3/9] drm/mediatek: add ddp component AAL1 Stu Hsieh
2018-05-28 7:03 ` CK Hu
2018-05-28 6:38 ` [PATCH v4 4/9] drm/mediatek: add ddp component OD1 Stu Hsieh
2018-05-28 7:07 ` CK Hu
2018-05-28 6:38 ` [PATCH v4 5/9] drm/mediatek: add ddp component PWM1 Stu Hsieh
2018-05-28 7:08 ` CK Hu
2018-05-28 6:38 ` [PATCH v4 6/9] drm/mediatek: add ddp component PWM2 Stu Hsieh
2018-05-28 7:09 ` CK Hu
2018-05-28 6:38 ` [PATCH v4 7/9] drm/mediatek: add connection from OD1 to RDMA1 Stu Hsieh
2018-05-28 7:13 ` CK Hu
2018-05-28 6:38 ` [PATCH v4 8/9] drm/mediatek: add third ddp path Stu Hsieh
2018-05-28 7:47 ` CK Hu
2018-06-08 8:31 ` Stu Hsieh
2018-05-28 6:38 ` [PATCH v4 9/9] drm/mediatek: Add support for mediatek SOC MT2712 Stu Hsieh
2018-05-28 7:53 ` CK Hu
2018-06-08 8:38 ` Stu Hsieh
2018-05-30 9:42 ` kbuild test robot
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=20180531024746.GA8356@rob-hp-laptop \
--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