On Friday 26 June 2009 20:25:42 Kevin Hilman wrote:
> Hans Verkuil <hverk...@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.
OK. I'll wait for the fixed patch and I'll then ask Mauro to merge this
platform patch and the vpif display driver into the v4l-dvb git tree.
> Also, please let me know the url and branch so I can be sure to handle
> any problems with other davinci patces going upstream.
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git#master
> Is this tree part of linux-next?
Yes.
> 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.
Regards,
Hans
--
Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
