From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/3] R8A7778/BOCK-W R-Car VIN driver support
Date: Thu, 27 Jun 2013 15:21:31 +0400 [thread overview]
Message-ID: <51CC203B.7040800@cogentembedded.com> (raw)
In-Reply-To: <20130627044838.GB28229@verge.net.au>
Hello.
On 27-06-2013 8:48, Simon Horman wrote:
>> Here's the set of 3 patches against the Simon Horman's 'renesas.git' repo,
>> 'renesas-next-20130620' tag. Here we add the VIN platform code working on
>> the R8A7778/BOCK-W with ML86V7667 video decoder.
>> [1/3] ARM: shmobile: r8a7778: add VIN support
>> [2/3] ARM: shmobile: BOCK-W: add VIN and ML86V7667 support
>> [3/3] ARM: shmobile: BOCK-W: enable VIN and ML86V7667 in defconfig
>> The patch containing OKI ML86V7667 video decoder driver has been removed
>> from the series as it should be applied to the 'media_tree.git' repo. The patch
>> containing the VIN PFC support has been also removed from the series and has
>> now been merged.
> is this series dependent on that patch or can it be applied independently?
No, it's dependent on the VIN driver patch for the platform data.
WBR, Sergei
prev parent reply other threads:[~2013-06-27 11:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 23:26 [PATCH v5 0/3] R8A7778/BOCK-W R-Car VIN driver support Sergei Shtylyov
2013-06-21 23:28 ` [PATCH v5 1/3] ARM: shmobile: r8a7778: add VIN support Sergei Shtylyov
2013-06-27 5:19 ` Kuninori Morimoto
2013-06-27 5:30 ` Simon Horman
2013-06-27 5:39 ` Kuninori Morimoto
2013-06-27 11:49 ` Sergei Shtylyov
2013-06-21 23:30 ` [PATCH v5 2/3] ARM: shmobile: BOCK-W: add VIN and ML86V7667 support Sergei Shtylyov
2013-06-27 5:25 ` Kuninori Morimoto
2013-06-27 11:45 ` Sergei Shtylyov
2013-06-21 23:31 ` [PATCH v5 3/3] ARM: shmobile: BOCK-W: enable VIN and ML86V7667 in defconfig Sergei Shtylyov
2013-06-27 4:48 ` [PATCH v5 0/3] R8A7778/BOCK-W R-Car VIN driver support Simon Horman
2013-06-27 11:21 ` Sergei Shtylyov [this message]
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=51CC203B.7040800@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--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;
as well as URLs for NNTP newsgroup(s).