From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: linux-sh@vger.kernel.org, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, devicetree@vger.kernel.org,
magnus.damm@gmail.com, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Add VIN and ADV7180 DT support for R8A7791/Henninger board
Date: Wed, 11 Jun 2014 16:41:33 +0400 [thread overview]
Message-ID: <53984E7D.8010909@cogentembedded.com> (raw)
In-Reply-To: <20140610235445.GE20738@verge.net.au>
Hello.
On 06/11/2014 03:54 AM, Simon Horman wrote:
>> Here's the set of 2 patches against Simon Horman's 'renesas.git' repo,
>> 'renesas-devel-v3.15-20140610' tag plus the Henninger I2C2 DT support patch
>> that I posted earlier. Here we add the VIN and ADV7180 video decoder device
>> tree support on the R8A7791/Henninger board. The patchset requires Ben Dooks'
>> adv7180, rcar_vin, and soc_camera DT support patches posted back in April in
>> order to work.
> I wonder what the status of those (driver?) patches are.
Someone in CodeThink is working on them, I was told. I had to fix them up
somewhat in order for them to compile.
> In general I prefer bindings to be accepted before they are used.
No argument here. I just have my own schedule.
WBR, Sergei
next prev parent reply other threads:[~2014-06-11 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 23:04 [PATCH 0/2] Add VIN and ADV7180 DT support for R8A7791/Henninger board Sergei Shtylyov
2014-06-10 23:06 ` [PATCH 1/2] ARM: shmobile: r8a7791: add VIN DT support Sergei Shtylyov
2014-06-11 23:53 ` Sergei Shtylyov
2014-06-10 23:07 ` [PATCH 2/2] ARM: shmobile: henninger: add VIN0/ADV7180 " Sergei Shtylyov
2014-06-10 23:54 ` [PATCH 0/2] Add VIN and ADV7180 DT support for R8A7791/Henninger board Simon Horman
2014-06-11 12:41 ` Sergei Shtylyov [this message]
2014-06-12 0:19 ` 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=53984E7D.8010909@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=horms@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).