From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] ARM: OMAP2+: PM: core support for SMPS regulators for v3.4
Date: Thu, 8 Mar 2012 16:32:18 -0800 [thread overview]
Message-ID: <20120309003217.GB12083@atomide.com> (raw)
In-Reply-To: <87399jc6cj.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [120308 09:37]:
> Tony Lindgren <tony@atomide.com> writes:
>
> > * Kevin Hilman <khilman@ti.com> [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@opensource.wolfsonmicro.com> [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
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: PM: core support for SMPS regulators for v3.4
Date: Thu, 8 Mar 2012 16:32:18 -0800 [thread overview]
Message-ID: <20120309003217.GB12083@atomide.com> (raw)
In-Reply-To: <87399jc6cj.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [120308 09:37]:
> Tony Lindgren <tony@atomide.com> writes:
>
> > * Kevin Hilman <khilman@ti.com> [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@opensource.wolfsonmicro.com> [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
next prev parent reply other threads:[~2012-03-09 0:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 20:14 [GIT PULL] ARM: OMAP2+: PM: core support for SMPS regulators for v3.4 Kevin Hilman
2012-03-07 20:14 ` Kevin Hilman
2012-03-08 2:18 ` Tony Lindgren
2012-03-08 2:18 ` Tony Lindgren
2012-03-08 18:09 ` Kevin Hilman
2012-03-08 18:09 ` Kevin Hilman
2012-03-09 0:32 ` Tony Lindgren [this message]
2012-03-09 0:32 ` Tony Lindgren
2012-03-09 11:47 ` Mark Brown
2012-03-09 11:47 ` Mark Brown
2012-03-09 15:29 ` Kevin Hilman
2012-03-09 15:29 ` Kevin Hilman
2012-03-11 20:42 ` Mark Brown
2012-03-11 20:42 ` Mark Brown
2012-03-12 17:26 ` Kevin Hilman
2012-03-12 17:26 ` Kevin Hilman
2012-03-12 17:32 ` Mark Brown
2012-03-12 17:32 ` Mark Brown
2012-03-12 23:28 ` Kevin Hilman
2012-03-12 23:28 ` Kevin Hilman
2012-03-27 13:57 ` Grazvydas Ignotas
2012-03-27 13:57 ` Grazvydas Ignotas
2012-03-27 17:04 ` Tony Lindgren
2012-03-27 17:04 ` Tony Lindgren
2012-03-27 17:49 ` Kevin Hilman
2012-03-27 17:49 ` Kevin Hilman
2012-04-03 18:44 ` Tony Lindgren
2012-04-03 18:44 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120309003217.GB12083@atomide.com \
--to=tony@atomide.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.