From: Kevin Hilman <khilman@deeprootsystems.com>
To: Chaithrika U S <chaithrika@ti.com>
Cc: linux-media@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
Manjunath Hadli <mrh@ti.com>, Brijesh Jadav <brijesh.j@ti.com>
Subject: Re: [PATCH] Subject: [PATCH v3 1/4] ARM: DaVinci: DM646x Video: Platform and board specific setup
Date: Fri, 26 Jun 2009 11:36:14 -0700 [thread overview]
Message-ID: <87d48qetb5.fsf@deeprootsystems.com> (raw)
In-Reply-To: <87ljneeti5.fsf@deeprootsystems.com> (Kevin Hilman's message of "Fri\, 26 Jun 2009 11\:32\:02 -0700")
Kevin Hilman <khilman@deeprootsystems.com> writes:
> Chaithrika U S <chaithrika@ti.com> writes:
>
>> Platform specific display device setup for DM646x EVM
>>
>> Add platform device and resource structures. Also define a platform specific
>> clock setup function that can be accessed by the driver to configure the clock
>> and CPLD.
>>
>> This patch is dependent on a patch submitted earlier, which adds
>> Pin Mux and clock definitions for Video on DM646x.
>>
>> Signed-off-by: Manjunath Hadli <mrh@ti.com>
>> Signed-off-by: Brijesh Jadav <brijesh.j@ti.com>
>> Signed-off-by: Chaithrika U S <chaithrika@ti.com>
>> ---
>> Applies to Davinci GIT tree
>
> Needs an update to apply to current linus or davinci git.
Please ignore this review, I see there was a newer version posted.
Will review shortly.
Sorry for the confusion.
Kevin
prev parent reply other threads:[~2009-06-26 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 13:25 [PATCH] Subject: [PATCH v3 1/4] ARM: DaVinci: DM646x Video: Platform and board specific setup Chaithrika U S
2009-06-22 8:14 ` chaithrika
2009-06-26 18:10 ` Hans Verkuil
2009-06-26 18:25 ` Kevin Hilman
2009-06-26 18:42 ` Hans Verkuil
2009-06-26 18:32 ` Kevin Hilman
2009-06-26 18:36 ` Kevin Hilman [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=87d48qetb5.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=brijesh.j@ti.com \
--cc=chaithrika@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-media@vger.kernel.org \
--cc=mrh@ti.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