>> >> This is the version v2 of the patch series. This is the reworked >> version of the driver based on comments received against the last >> version of the patch. > >I'll be glad to see this get to mainline ... it's seeming closer >and closer! > >What's the merge plan though? I had hopes for 2.6.31.real-soon >but several of the later patches comment > Not sure if it can go in 2.6.31, but this has less comments to address then I can send a updated version next week. 2.6.32 is the targeted release. > > Applies to Davinci GIT Tree > >which implies "not -next". DM355 patches are in the "-next" tree. > >Is this just an oversight (tracking -next can be a PITA!) or is >there some other dependency? > One dependency is the tvp514x sub device patch migration patch from Vaibhav. This is put for review, but couldn't see any comments. I have split the patches such that v4l2 part can applies independently followed by platform part. All of the platform part has "Applies to Davinci GIT tree" in the patch description and v4l2 part has "Applies to v4l-dvb". The v4l2 part can go with out the platform changes, but platform part is dependent on the v4l2 part. I am not sure if I have answered your question. >- > -- 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
