linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Multi Cluster Power Management infrastructure
Date: Sat, 6 Apr 2013 18:46:52 +0100	[thread overview]
Message-ID: <CACxGe6sg==Zb56vVXeege29HovOpwtcosJk7ssw=wGCLV38j3A@mail.gmail.com> (raw)
In-Reply-To: <201304052233.25630.arnd@arndb.de>

On Fri, Apr 5, 2013 at 9:33 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Friday 05 April 2013, Russell King - ARM Linux wrote:
>>
>> Now, I'm currently on holiday.  I'm going to be on holday until after
>> mid-April.  I'm not pulling anything until then.  I'm not applying anything
>> until then.  I'm not even reading this mailbox - and given current mail
>> rates at 300-400 messages per day, I will *not* be reading back over a
>> fortnights worth of email.
>
> I haven't reviewed the patches before, and only heard of the controversy
> from Nico's email yesterday. Independent of your personal situation and
> who implemented the code, I think it's clear that a lot of people (not
> just Linaro) want to see it get merged and not having it upstream is
> blocking platform specific code from getting put into arm-soc.
>
> Since you are currently on holiday, I think it's best if we at least put
> it into asm-soc as a for-rmk/mcpm branch in order to give it coverage
> in linux-next and let us merge the dependent platform code into "late"
> branches for 3.10. I still hope the nontechnical issues can be resolved
> in time to let you pull it into your tree before the merge window.

I agree. This makes the most sense. There is no reason for mcpm to be
excluded from linux-next before this issue is resolved.

g.

  parent reply	other threads:[~2013-04-06 17:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 16:41 [GIT PULL] Multi Cluster Power Management infrastructure Nicolas Pitre
2013-03-28 13:48 ` Lorenzo Pieralisi
2013-04-03  3:00   ` Nicolas Pitre
2013-04-05  2:03     ` Nicolas Pitre
2013-04-05  9:41       ` Russell King - ARM Linux
2013-04-05 13:30         ` Nicolas Pitre
2013-04-07  0:23           ` Russell King - ARM Linux
2013-04-07  0:32             ` Russell King - ARM Linux
2013-04-05 20:33         ` Arnd Bergmann
2013-04-05 21:07           ` Olof Johansson
2013-04-05 21:32             ` Nicolas Pitre
2013-04-06 17:46           ` Grant Likely [this message]
2013-04-07  0:02           ` Russell King - ARM Linux
2013-04-09  5:20             ` Nicolas Pitre
  -- strict thread matches above, loose matches on Subject: below --
2013-02-06 19:12 Nicolas Pitre

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='CACxGe6sg==Zb56vVXeege29HovOpwtcosJk7ssw=wGCLV38j3A@mail.gmail.com' \
    --to=grant.likely@secretlab.ca \
    --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).