>> Is this the way to proceed or should I send a fix on top of it? This >> patch is merged in 'for_v3.5', if Mauro reverts it and I send a new >> version, would it be also merged 'for_v3.5' or should it wait for >> version 3.6? > > I think, it would be better to revert and re-do it for the following > reason: since neither you nor me can test those pass-through cases, I > think, it is easier to review patches and try to avoid regressions by > looking at patches, that take you from a (presumably working) state A step > by step to a state B, where each patch is seemingly correct, than by > looking at a patch "a" that introduces a breakage and "b" that hopefully > should fix it back. All right. Then Mauro can revert this patch and I'll get my hands on a new version whenever I have some spare time. Sorry for the inconvenience. Regards. -- Javier Martin Vista Silicon S.L. CDTUC - FASE C - Oficina S-345 Avda de los Castros s/n 39005- Santander. Cantabria. Spain +34 942 25 32 60 www.vista-silicon.com -- 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
