On Tuesday 15 March 2011, Mark Brown wrote: > > 2) Basically make a copy. This would look like the original patch set did when we went > > A third option is just to lift everything out of staging roughly as it > is now with anything that definitely needs redoing dropped, addressing > any review comments for mainline but not doing much else, and then > resume working on adding additional stuff. It sounds like the userspace > interfaces that are there at present are mostly OK and most of the > issues are in-kernel? > > You could perhaps have a Kconfig control for disabling any experimental > features in the API if you want to give people hints about areas that > are likely to churn. I agree, that sounds like a good idea for preparing the code before a split. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
