On Mon, 2013-04-15 at 17:26 +0100, Mark Brown wrote: > On Sat, Apr 13, 2013 at 11:01:18PM +0200, Johannes Berg wrote: > > On Sat, 2013-04-13 at 07:13 -0700, Luis R. Rodriguez wrote: > > > > This backports the latest regulator drivers for kernels >= 3.4. > > > We enable the regulator only on kernels >= 3.4 given that > > > it relies on the new probe deferral mechanism which would > > > otherwise mean having to support drivers that do not probe > > > correctly. Note that 3.2 had a base regulator implementation > > > but that was just stubs. > > > Applied. > > Please let's at least discuss the issues here, I'm not sure what this is > supposed to do but the analysis of the subsystem didn't seem complete. I wouldn't worry about it too much. For some reason (media drivers related?) Luis decided that it was worth including this in the backports project (see http://backports.wiki.kernel.org) and I am currently maintaining the git tree for that, at least while I was doing some refactoring. I do notice that it doesn't quite work, there are a lot of unresolved symbols :) If you think you'd be impacted by this because users demand support from you for the backport or whatever I can revert this (or probably just remove it from the copy list for now.) I don't really have an opinion on it, I'm doing this because I'm interested in one specific wireless driver. 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
