From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpuidle: add maintainer entry
Date: Wed, 24 Apr 2013 09:55:27 -0700 [thread overview]
Message-ID: <87k3nr50n4.fsf@linaro.org> (raw)
In-Reply-To: <1366810463-17495-1-git-send-email-daniel.lezcano@linaro.org> (Daniel Lezcano's message of "Wed, 24 Apr 2013 15:34:23 +0200")
Rafael,
Daniel Lezcano <daniel.lezcano@linaro.org> writes:
[...]
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 61677c3..effa0f3 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2206,6 +2206,13 @@ S: Maintained
> F: drivers/cpufreq/
> F: include/linux/cpufreq.h
>
> +CPUIDLE DRIVERS
> +M: Rafael J. Wysocki <rjw@sisk.pl>
> +L: linux-pm at vger.kernel.org
> +S: Maintained
> +F: drivers/cpuidle/*
> +F: include/linux/cpuidle.h
What do you think about having Daniel listed here as a co-maintainer?
He has been driving a significant consolidation effort, and will
continue to do that, so I think he should help take care of this area
and ensure all drivers are moving in the right direction.
Kevin
next prev parent reply other threads:[~2013-04-24 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 13:34 [PATCH] cpuidle: add maintainer entry Daniel Lezcano
2013-04-24 13:55 ` Jason Cooper
2013-04-24 14:23 ` Andrew Lunn
2013-04-24 16:55 ` Kevin Hilman [this message]
2013-04-25 12:09 ` Linus Walleij
2013-04-25 18:27 ` Rafael J. Wysocki
2013-04-26 8:32 ` Linus Walleij
2013-04-26 10:53 ` Daniel Lezcano
2013-04-24 17:50 ` Rob Herring
2013-04-25 6:45 ` Daniel Lezcano
2013-04-25 6:49 ` Viresh Kumar
2013-04-25 7:06 ` Daniel Lezcano
2013-04-25 15:50 ` Rob Herring
2013-04-25 16:32 ` Daniel Lezcano
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=87k3nr50n4.fsf@linaro.org \
--to=khilman@linaro.org \
--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).