Hans Verkuil <hverkuil@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
