Arnd Bergmann <arnd.bergmann@xxxxxxxxxx> 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@xxxxxx> (commit_signer:8/10=80%) > Len Brown <len.brown@xxxxxxxxx> (commit_signer:7/10=70%) > Trinabh Gupta <g.trinabh@xxxxxxxxx> (commit_signer:4/10=40%) > Arjan van de Ven <arjan@xxxxxxxxxxxxxxx> (commit_signer:4/10=40%) > Deepthi Dharwar <deepthi@xxxxxxxxxxxxxxxxxx> (commit_signer:4/10=40%) > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
