linux-kernel - Re: [PATCH v8 0/8] Consolidate cpuidle functionality

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.02.1203202146131.24151@xanadu.home>
Date:	Tue, 20 Mar 2012 22:23:53 -0400 (EDT)
From:	Nicolas Pitre <nicolas.pitre@...aro.org>
To:	Amit Kucheria <amit.kucheria@...aro.org>
cc:	Kevin Hilman <khilman@...com>,
	Arnd Bergmann <arnd.bergmann@...aro.org>,
	Robert Lee <rob.lee@...aro.org>, len.brown@...el.com,
	Andrew Morton <akpm@...ux-foundation.org>, rjw@...k.pl,
	robherring2@...il.com, Baohua.Song@....com,
	nicolas.ferre@...el.com, linux@...im.org.za, kgene.kim@...sung.com,
	amit.kachhap@...aro.org, magnus.damm@...il.com, nsekhar@...com,
	daniel.lezcano@...aro.org, mturquette@...aro.org,
	vincent.guittot@...aro.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linaro-dev@...ts.linaro.org,
	patches@...aro.org, deepthi@...ux.vnet.ibm.com,
	broonie@...nsource.wolfsonmicro.com,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	jean.pihet@...oldbits.com, venki@...gle.com, ccross@...gle.com,
	g.trinabh@...il.com, kernel@...tstofly.org, lethal@...ux-sh.org,
	jon-hunter@...com, tony@...mide.com, linux-omap@...r.kernel.org,
	linux-sh@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v8 0/8] Consolidate cpuidle functionality

On Wed, 21 Mar 2012, Amit Kucheria wrote:

> On Wed, Mar 21, 2012 at 12:48 AM, Kevin Hilman <khilman@...com> 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.
> >
> 
> I don't mean to be piling on to Len here, but Daniel Lezcano too has a
> bunch of clean ups that didn't get any maintainer review for over two
> months. He has now refreshed them for 3.3 and is getting ready to send
> them out again. We (Linaro) expect to be spending a lot of time on
> cpuidle in the future and would be glad to help review, test and
> collect patches into a tree for Linus/Andrew to pull while we wait for
> Len to respond or another maintainer to emerge.

As I advised recently, it is usually a good idea for the person/group 
who is working the most on a subsystem to simply take the lead and 
become the new maintainer.  Waiting for another maintainer to emerge 
could be compared to cowardice.


Nicolas