From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: linux-renesas-soc@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, devicetree@vger.kernel.org,
magnus.damm@gmail.com, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: wheat: add DU support
Date: Fri, 16 Sep 2016 12:11:39 +0200 [thread overview]
Message-ID: <20160916101139.GI14562@verge.net.au> (raw)
In-Reply-To: <ba5b2f8e-13f8-6c7d-17c1-44988d30a947@cogentembedded.com>
On Mon, Sep 12, 2016 at 08:52:40PM +0300, Sergei Shtylyov wrote:
> On 09/02/2016 12:29 AM, Sergei Shtylyov wrote:
>
> >Define the Wheat board dependent part of the DU device node.
> >Add the device nodes for the Analog Devices ADV7513 HDMI transmitters
> >connected to DU0/1. Add the necessary subnodes to interconnect DU with
> >HDMI transmitters/connectors.
> >
> >Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> >
> >---
> >This patch is against the 'renesas-devel-20160901-v4.8-rc4' of Simon Horman's
> >'renesas.git' repo plus the Wheat CAN and SDHI patches posted earlier...
> >The path depends on the 2 DRM patches just posted in order to work correctly!
>
> In principle, both these patches have been queued by the maintainers...
> Simon, are you going to wait till they hit media_tree.git? Linus' tree?
I don't think that is necessary. I was waiting for some review.
But in any case it looks like this patch no longer applies cleanly.
Could you rebase?
next prev parent reply other threads:[~2016-09-16 10:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 20:18 [PATCH 0/3] Add R8A7792/Blanche CAN support Sergei Shtylyov
2016-07-14 20:19 ` [PATCH 1/3] ARM: dts: r8a7792: add CAN clocks Sergei Shtylyov
2016-07-15 3:19 ` Geert Uytterhoeven
2016-07-14 20:20 ` [PATCH 2/3] ARM: dts: r8a7792: add CAN support Sergei Shtylyov
2016-07-15 3:21 ` Geert Uytterhoeven
2016-07-14 20:21 ` [PATCH 3/3] ARM: dts: blanche: add CAN0 support Sergei Shtylyov
2016-07-18 2:10 ` [PATCH 0/3] Add R8A7792/Blanche CAN support Simon Horman
2016-09-01 21:29 ` [PATCH] ARM: dts: wheat: add DU support Sergei Shtylyov
2016-09-12 17:52 ` Sergei Shtylyov
2016-09-16 10:11 ` Simon Horman [this message]
[not found] ` <34968644.DhifNderY8-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2016-08-29 20:11 ` [PATCH] ARM: dts: wheat: add CAN support Sergei Shtylyov
2016-09-03 21:50 ` Sergei Shtylyov
2016-09-05 12:03 ` Simon Horman
2016-08-30 22:24 ` [PATCH] ARM: dts: wheat: add SDHI0 support Sergei Shtylyov
[not found] ` <1659137.gEKJxNrmrk-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2016-08-31 7:06 ` Geert Uytterhoeven
2016-09-03 21:49 ` Sergei Shtylyov
2016-09-05 12:07 ` Simon Horman
2016-09-22 21:06 ` [PATCH v2] ARM: dts: wheat: add DU support Sergei Shtylyov
2016-09-23 7:37 ` Simon Horman
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=20160916101139.GI14562@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).