linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-acpi@vger.kernel.org, linux-pm@lists.linux-foundation.org,
	Lists Linaro-dev <linaro-dev@lists.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Kevin Hilman <khilman@ti.com>,
	Peter De Schrijver <pdeschrijver@nvidia.com>,
	Amit Kucheria <amit.kucheria@linaro.org>,
	linux-next@vger.kernel.org, Colin Cross <ccross@android.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Rob Lee <rob.lee@linaro.org>, "lenb@kernel.org" <lenb@kernel.org>
Subject: Re: linux-next : cpuidle - could you add my tree please
Date: Mon, 2 Jul 2012 21:49:36 +0200	[thread overview]
Message-ID: <201207022149.36629.rjw@sisk.pl> (raw)
In-Reply-To: <4FF19947.3040608@linaro.org>

On Monday, July 02, 2012, Daniel Lezcano wrote:
> 
> On 07/02/2012 11:09 AM, Linus Walleij wrote:
> > On Mon, Jun 25, 2012 at 3:27 PM, Daniel Lezcano
> > <daniel.lezcano@linaro.org> wrote:
> > 
> >> we discussed last week to put in place a tree grouping the cpuidle
> >> modifications [1]. Is it possible to add the tree ?
> >>
> >> git://git.linaro.org/people/dlezcano/cpuidle-next.git #cpuidle-next
> > 
> > Thanks for doing this.
> > 
> > Since MAINTAINERS is lacking a listed maintainer for cpuidle,
> > are you also going to add yourself as maintainer and list this
> > tree in that file, or is this a one-time exercise?
> 
> I will be glad to do that if Len and Rafael agree on that.

Len Brown has been a cpuidle maintainer for some time now.  Moreover,
he's been taking patches, but Linus refused to pull his entire tree during the
last merge window (as you probably know).  I honestly don't think this is
a good enough reason for replacing him as a cpuidle maintainer by force.

So, you should ask Len whether or not he's willing to pass the cpuidle
maintenance to someone else.

I know that Len hasn't been responsive recently, but I also know that he
_does_ respond to inquiries sent directly to him.

Thanks,
Rafael

  reply	other threads:[~2012-07-02 19:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18  8:40 cpuidle future and improvements Daniel Lezcano
2012-06-18 11:54 ` Deepthi Dharwar
2012-06-18 12:35   ` Daniel Lezcano
2012-06-18 12:53     ` Peter De Schrijver
2012-06-18 12:55       ` Daniel Lezcano
2012-06-18 13:06         ` Jean Pihet
2012-06-18 13:26           ` Daniel Lezcano
2012-06-18 13:30 ` [linux-pm] " a0393909
2012-06-25 12:58   ` Shilimkar, Santosh
2012-06-25 13:10     ` Daniel Lezcano
2012-06-25 13:17       ` Shilimkar, Santosh
2012-06-25 13:27   ` linux-next : cpuidle - could you add my tree please Daniel Lezcano
2012-06-25 22:53     ` Stephen Rothwell
2012-07-02  9:09     ` Linus Walleij
2012-07-02 12:51       ` Daniel Lezcano
2012-07-02 19:49         ` Rafael J. Wysocki [this message]
2012-07-02 22:14           ` Daniel Lezcano
2012-07-03  8:59             ` Rafael J. Wysocki
2012-07-03 12:56               ` Daniel Lezcano
2012-07-03 13:19                 ` Stephen Rothwell
2012-07-03 13:25                   ` Daniel Lezcano
2012-07-03 16:54                     ` Rafael J. Wysocki
2012-07-05 13:33                       ` Daniel Lezcano
2012-07-03 19:20             ` Linus Walleij
2012-07-03 19:33               ` Rafael J. Wysocki
2012-07-02 20:04     ` Rafael J. Wysocki
2012-06-18 18:15 ` cpuidle future and improvements Colin Cross
2012-06-18 19:00   ` Daniel Lezcano
2012-06-25 12:54   ` Daniel Lezcano
2012-07-11 14:00     ` [linux-pm] " Kevin Hilman

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=201207022149.36629.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=amit.kucheria@linaro.org \
    --cc=ccross@android.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=khilman@ti.com \
    --cc=lenb@kernel.org \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pdeschrijver@nvidia.com \
    --cc=rob.lee@linaro.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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).