Johannes Stezenbach wrote:
There is a fair amount of code duplication. A better aproach would be to allocate buffers once in cinergyt2_fe_attach() (add them to struct cinergyt2_fe_state).
Yes, but first I have to investigate why tuning is still quite unreliable (ie, more unreliable than in 2.6.29). Am I really the only one who has those problems with the Cinergy T2 driver in 2.6.30? -- 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
