* Kevin Hilman <khilman@xxxxxx> [120308 09:37]: > Tony Lindgren <tony@xxxxxxxxxxx> writes: > > > * Kevin Hilman <khilman@xxxxxx> [120307 11:42]: > >> Tony, > >> > >> Please pull the following support for using regulators to control the > >> on-chip VC/VP managed voltage domains. > >> > >> The regulator driver support for this is already queued in the regulator > >> tree, and this is the supporting core work. > >> > >> This combined with the CPUfreq changes to use the regulator framework > >> will finally result in MPU DVFS working in mainline. > > > > Nice.. However this one might be missing some header changes? > > Oh, that's because it depends on the regulator core changes that are in > Mark's regulator tree. You need the for-next branch of : > > git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git > > For this to compile correctly. > > Sorry, I should've been more clear above about the build dependency. Hmm just checking.. Recently Mark replied to Peter: * Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> [120228 02:17]: > On Tue, Feb 28, 2012 at 09:40:10AM +0200, Peter Ujfalusi wrote: > > > NOTE: this series has been generated agains Takashi's topic/asoc branch merged > > with Mark's for-next branch since this series depends on changes in Marks' > > branch, but not yet pulled by Takashi (snd_soc_add_dai_controls implementation > > from Liam). > > Never base *anything* off my for-next branch, it gets rebuilt regularly. So can you guys please confirm that if is indeed an immutable commit to use as a base to merge in something? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
