From: Kevin Hilman <khilman@ti.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 0/8] Consolidate cpuidle functionality
Date: Tue, 20 Mar 2012 23:56:51 +0000 [thread overview]
Message-ID: <87ty1ix1vg.fsf@ti.com> (raw)
In-Reply-To: <201203202305.37952.arnd.bergmann@linaro.org> (Arnd Bergmann's message of "Tue, 20 Mar 2012 23:05:37 +0000")
Arnd Bergmann <arnd.bergmann@linaro.org> writes:
> On Tuesday 20 March 2012, Kevin Hilman wrote:
>> Maybe it's time that drivers/cpuidle gets a maintainer. With lots of
>> discussions of scheduler changes that affect load estimation, I suspect
>> we're all going to have a bit of CPUidle work to do in the
>> not-so-distant future.
>
> Hmm, according to the script, you are the maintainer ;-)
doh, I knew I should've kept quiet :/
> $ scripts/get_maintainer.pl -f drivers/cpuidle/cpuidle.c
> Kevin Hilman <khilman@ti.com> (commit_signer:8/10€%)
> Len Brown <len.brown@intel.com> (commit_signer:7/10p%)
> Trinabh Gupta <g.trinabh@gmail.com> (commit_signer:4/10@%)
> Arjan van de Ven <arjan@linux.intel.com> (commit_signer:4/10@%)
> Deepthi Dharwar <deepthi@linux.vnet.ibm.com> (commit_signer:4/10@%)
>
> While I realize that the get_maintainers.pl is not the final word,
> you could be the acting cpuidle maintainer for this merge window
> and send the pull request.
Not exactly the outcome I was hoping for (I have enough stuff to look
after at the moment.)
However, if you think it would help and won't be seen as a take over
attempt (I don't want to maintain CPUidle), I can possibly do it for
this merge window.
Before doing that though, I'll need give this series a final once over
before I'm willing to send a potentially flame-attracting pull request.
Kevin
next prev parent reply other threads:[~2012-03-20 23:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 20:22 [PATCH v8 0/8] Consolidate cpuidle functionality Robert Lee
2012-03-20 20:22 ` [PATCH v8 1/8] cpuidle: Add common time keeping and irq enabling Robert Lee
2012-03-20 20:22 ` [PATCH v8 2/8] ARM: at91: Consolidate time keeping and irq enable Robert Lee
2012-03-20 20:22 ` [PATCH v8 3/8] ARM: kirkwood: " Robert Lee
2012-03-20 20:22 ` [PATCH v8 4/8] ARM: davinci: " Robert Lee
2012-03-21 14:28 ` Rob Lee
2012-03-21 14:36 ` Rob Lee
2012-03-21 14:36 ` Amit Kucheria
2012-03-20 20:22 ` [PATCH v8 5/8] ARM: omap: Consolidate OMAP3 " Robert Lee
2012-03-20 20:22 ` [PATCH v8 6/8] ARM: omap: Consolidate OMAP4 " Robert Lee
2012-03-20 20:22 ` [PATCH v8 7/8] ARM: shmobile: Consolidate " Robert Lee
2012-03-20 20:22 ` [PATCH v8 8/8] SH: " Robert Lee
2012-03-20 21:58 ` [PATCH v8 0/8] Consolidate cpuidle functionality Arnd Bergmann
2012-03-20 22:48 ` Kevin Hilman
2012-03-20 23:05 ` Arnd Bergmann
2012-03-20 23:56 ` Kevin Hilman [this message]
2012-03-20 23:06 ` Amit Kucheria
2012-03-20 23:58 ` Rafael J. Wysocki
2012-03-21 2:50 ` Deepthi Dharwar
2012-03-21 4:53 ` Len Brown
2012-03-21 2:23 ` Nicolas Pitre
2012-03-21 0:10 ` Kevin Hilman
2012-03-21 1:45 ` Nicolas Pitre
2012-03-21 4:45 ` Rob Lee
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=87ty1ix1vg.fsf@ti.com \
--to=khilman@ti.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).