From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: PM: core support for SMPS regulators for v3.4
Date: Fri, 9 Mar 2012 11:47:36 +0000 [thread overview]
Message-ID: <20120309114731.GA3273@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120309003217.GB12083@atomide.com>
On Thu, Mar 08, 2012 at 04:32:18PM -0800, Tony Lindgren wrote:
> * Kevin Hilman <khilman@ti.com> [120308 09:37]:
> > Tony Lindgren <tony@atomide.com> writes:
> > 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:
...
> So can you guys please confirm that if is indeed an immutable
> commit to use as a base to merge in something?
Absolutely not, the for-next branch is rebuilt frequently especially
since it includes stuff sent to Linus and he complained about bugfixes
merged up into development code. What is the actual dependency here?
The topic branches are more or less static, though some more than
others.
In general you should warn people if you've got a dependency on their
tree, it makes life easier.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120309/1cadb9fb/attachment-0001.sig>
next prev parent reply other threads:[~2012-03-09 11:47 UTC|newest]
Thread overview: 14+ 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-08 2:18 ` Tony Lindgren
2012-03-08 18:09 ` Kevin Hilman
2012-03-09 0:32 ` Tony Lindgren
2012-03-09 11:47 ` Mark Brown [this message]
2012-03-09 15:29 ` Kevin Hilman
2012-03-11 20:42 ` Mark Brown
2012-03-12 17:26 ` Kevin Hilman
2012-03-12 17:32 ` Mark Brown
2012-03-12 23:28 ` Kevin Hilman
2012-03-27 13:57 ` Grazvydas Ignotas
2012-03-27 17:04 ` Tony Lindgren
2012-03-27 17:49 ` Kevin Hilman
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=20120309114731.GA3273@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).