> > > It can be worth doing anyway with a subsystem that's actively developed > > > since sometimees the dependencies are the other way - the APIs in Linus' > > > tree may have gone away. > > > Then what happens if the tree that your patch finally gets sucked into > > is pulled before the one you've written your code against? I'd say > > basing your code on -next is generally a bad idea. > > Submitters should defintely at the very least be checking against the > subsystem tree (since that's what they're really submitting against) - > it's always annoying when someone submits code that either doesn't > apply or fails to build with the current tree.
+1 -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
