On Sat, 2013-10-26 at 11:45 +0200, Luis R. Rodriguez wrote: > > Yes moving the dependencies is easier than backporting the code which > > does not work any more. ;-) The problem here is that the regulator core > > can not be backported, because it is always build into the kernel and > > not as a module. > As for the issues with some functionality on the regulator > drivers requiring functionality from future kernels as its always > built-in, that can be addressed if we add support for non-modular > solutions on backports. I don't think that's actually true - the regulator drivers may require being built-in, but there are probably good reasons for that like multiple other modules accessing them. So updating them in a backport and building them in wouldn't really help since now you'd have two identical regulators that conflict and have different users. And if you tried to backport it into the tree and make it the only regulator driver, you'd now have to forward-port all the remaining in-tree users as well, which seems unreasonable too. The only usage would seem to be building it including *all* users as part of the backport, but that seems somewhat unlikely? johannes -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
