On Fri, Dec 17, 2010 at 02:12:46PM -0800, Stephen Warren wrote: > This patchset is against the current linux-tegra-2.6.36 tree, since > the original code was against 2.6.36, and linux-tegra-2.6.36 is where I was > originally tasked with getting the code. > Once I've resolved any glaring issues with that, I was going to target > mainline, and then continue further development there. Mainly this patchset > checkpoints my work before porting to the recent ASoC API changes. > Does that seem like a reasonable plan? Honestly if you're starting out here it's probably easier to backport current ASoC into 2.6.36 (it has relatively few external dependencies and should drop in fairly neatly, I can help with that if need be) and get the benefits of the newer APIs. This... > Note: Having this in linux-tegra-2.6.36 was originally useful because ChromeOS > was branching from there, so would have to carry fewer patches relative to > anything that made it there. However, it looks like ChromeOS will be switching > to more recent kernels in the very near term, so the benefit of having code in > linux-tegra-2.6.36 is diminished. ...means you get to skip the pain of having to update to newer APIs immediately you get a new kernel version, and getting the work into mainline means that for future API updates a lot of the work will get done for you as mainline is updated. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
