From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
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 v2 0/2] Add VIN and ADV7180 device tree support for R8A7791/Henninger board
Date: Mon, 4 Aug 2014 16:08:13 +0900 [thread overview]
Message-ID: <20140804070813.GB1889@verge.net.au> (raw)
In-Reply-To: <201408020402.14560.sergei.shtylyov@cogentembedded.com>
On Sat, Aug 02, 2014 at 04:02:13AM +0400, Sergei Shtylyov wrote:
> Hello.
>
> Here's the set of 2 patches against Simon Horman's 'renesas.git' repo,
> 'renesas-devel-v3.16-rc7-20140731v2' tag. Here we add the VIN and ADV7180 video
> decoder device tree support on the R8A7791/Henninger board. The patchset
> requires Ben Dooks' 'rcar_vin' and 'soc_camera' DT support patches already
> merged to the 'media_tree.git' in order to work.
>
> [1/2] ARM: shmobile: r8a7791: add VIN DT support
> [2/2] ARM: shmobile: henninger: add VIN0/ADV7180 DT support
Thanks, I have queued these up for v3.18.
next prev parent reply other threads:[~2014-08-04 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 0:02 [PATCH v2 0/2] Add VIN and ADV7180 device tree support for R8A7791/Henninger board Sergei Shtylyov
2014-08-02 0:04 ` [PATCH v2 1/2] ARM: shmobile: r8a7791: add VIN DT support Sergei Shtylyov
2014-08-02 0:05 ` [PATCH v2 2/2] ARM: shmobile: henninger: add VIN0/ADV7180 " Sergei Shtylyov
2014-08-04 7:08 ` Simon Horman [this message]
[not found] ` <201408020402.14560.sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-08-06 18:38 ` [PATCH] ARM: shmobile: koelsch: add VIN1/ADV7180 " sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8
2014-08-07 0:47 ` Simon Horman
2014-08-07 4:01 ` Magnus Damm
2014-08-07 15:31 ` Sergei Shtylyov
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=20140804070813.GB1889@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--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 \
--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).