From: Kevin Hilman <khilman@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@sisk.pl, cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, robin.randhawa@arm.com,
Steve.Bannister@arm.com, Liviu.Dudau@arm.com,
charles.garcia-tobin@arm.com, arvind.chauhan@arm.com,
linaro-kernel@lists.linaro.org, patches@linaro.org,
arnd.bergmann@linaro.org, olof@lixom.net
Subject: Re: [PATCH V2] cpufreq: MAINTAINERS: Add co-maintainer
Date: Fri, 26 Apr 2013 09:55:08 -0700 [thread overview]
Message-ID: <87k3npz0yb.fsf@linaro.org> (raw)
In-Reply-To: <d62f23f626eaf334236cb9694c83ee4619460b76.1366980696.git.viresh.kumar@linaro.org> (Viresh Kumar's message of "Fri, 26 Apr 2013 18:23:16 +0530")
Viresh Kumar <viresh.kumar@linaro.org> writes:
> With prior discussions (Over private emails) with current Maintainer of cpufreq
> framework (Rafael), I am adding myself as a co-maintainer of cpufreq framework.
>
> This would mostly be for cpufreq core and ARM drivers but not restricted to
> them.
>
> This also adds path of the git tree where cpufreq patches are pulled in.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
As long as you continue to make an effort to ensure that the
platform-specific drivers have proper acks from platform-specific folks.
For ARM, this means not the arm-soc maintainers but the ARM subarch
maintianers.
Acked-by: Kevin Hilman <khilman@linaro.org>
> ---
> V1->V2:
> - Added path of git tree too.
> - Cc'd ARM SoC Maintainers.
>
> MAINTAINERS | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 68d376e..cbed63c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2211,9 +2211,11 @@ F: drivers/net/ethernet/ti/cpmac.c
>
> CPU FREQUENCY DRIVERS
> M: Rafael J. Wysocki <rjw@sisk.pl>
> +M: Viresh Kumar <viresh.kumar@linaro.org>
> L: cpufreq@vger.kernel.org
> L: linux-pm@vger.kernel.org
> S: Maintained
> +T: git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
> F: drivers/cpufreq/
> F: include/linux/cpufreq.h
next prev parent reply other threads:[~2013-04-26 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 12:53 [PATCH V2] cpufreq: MAINTAINERS: Add co-maintainer Viresh Kumar
2013-04-26 16:55 ` Kevin Hilman [this message]
2013-04-26 20:50 ` Rafael J. Wysocki
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=87k3npz0yb.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=arnd.bergmann@linaro.org \
--cc=arvind.chauhan@arm.com \
--cc=charles.garcia-tobin@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=olof@lixom.net \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
--cc=robin.randhawa@arm.com \
--cc=viresh.kumar@linaro.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