>> That's said, if I understood Devin wrong or if you now have plans to add some >> real code at the new ngene-av and ngene-eeprom files, that's fine for me. >> I'll happily accept a patch that moves that code to another file and enable >> the code to read eeprom and to use the AV part, even if you do it on separate >> patches, inside the same pull request. > > Hmm... this were badly written, partially due to a typo. So let me re-phrase it: > > If my understanding from Devin's chat were wrong and if you actually have plans to add some > working code at the new ngene-av and ngene-eeprom files, that's fine for me. > I'll happily accept a patch that moves that code to another file and enable > the code to read eeprom and to use the AV part, even if you do it on separate > patches, inside the same pull request. Correct, we plan to make significant changes to -av and -eeprom files (including the final removal of dead code). Pretty much every file in the ngene driver is getting major rework Regards, -- Steven Toth - Kernel Labs http://www.kernellabs.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
