From: Kevin Hilman <khilman@deeprootsystems.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: "chaithrika" <chaithrika@ti.com>,
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:25:42 -0700 [thread overview]
Message-ID: <87ws6yetsp.fsf@deeprootsystems.com> (raw)
In-Reply-To: <200906262010.31064.hverkuil@xs4all.nl> (Hans Verkuil's message of "Fri\, 26 Jun 2009 20\:10\:30 +0200")
Hans Verkuil <hverkuil@xs4all.nl> writes:
> On Monday 22 June 2009 10:14:30 chaithrika wrote:
>> Kevin,
>>
>> I think this patch has to be taken into DaVinci tree so that it
>> can be submitted upstream. This patch has to be present in the Linux
>> tree for Hans to prepare a pull request for DM646x display driver
>> patches.
>
> What are the plans for this patch? Will Kevin take care of this? In that
> case the v4l patches will have to wait until this patch is in Linus' git
> tree. Alternatively, we can pull this in via the v4l-dvb git tree. I think
> that is propably the easiest approach.
Hans, I'm ok if you pull this directly into v4l-dvb git. But first, I
there are a couple minor problems with this patch. I'll reply
to the original post.
Also, please let me know the url and branch so I can be sure to handle
any problems with other davinci patces going upstream.
Is this tree part of linux-next? I now have a 'for-next' branch
of DaVinci git which is included in linux-next so any potential
conflicts will be found there as well.
Thanks,
Kevin
next prev parent reply other threads:[~2009-06-26 18:25 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 [this message]
2009-06-26 18:42 ` Hans Verkuil
2009-06-26 18:32 ` Kevin Hilman
2009-06-26 18:36 ` Kevin Hilman
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=87ws6yetsp.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=hverkuil@xs4all.nl \
--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