From: Kevin Hilman <khilman@linaro.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: rjw@sisk.pl, linux-pm@vger.kernel.org,
linaro-kernel@lists.linaro.org, rob.herring@calxeda.com,
jason@lakedaemon.net, andrew@lunn.ch, nicolas.ferre@atmel.com,
plagnioj@jcrosoft.com, linux@maxim.org.za, kernel@pengutronix.de,
swarren@wwwdotorg.org, horms+renesas@verge.net.au,
josephl@nvidia.com, arnd@arndb.de,
linux-arm-kernel@lists.infradead.org, horms@verge.net.au,
magnus.damm@gmail.com, benh@kernel.crashing.org,
paulus@samba.org, kgene.kim@samsung.com,
linus.walleij@linaro.org, viresh.kumar@linaro.org,
lenb@kernel.org, nsekhar@ti.com, ben-linux@fluff.org
Subject: Re: [V2 PATCH] cpuidle: add maintainer entry
Date: Fri, 26 Apr 2013 09:49:46 -0700 [thread overview]
Message-ID: <87txmtz179.fsf@linaro.org> (raw)
In-Reply-To: <1366974344-26064-1-git-send-email-daniel.lezcano@linaro.org> (Daniel Lezcano's message of "Fri, 26 Apr 2013 13:05:44 +0200")
Daniel Lezcano <daniel.lezcano@linaro.org> writes:
> Currently the cpuidle drivers are spread across the different archs.
>
> The patch submission for cpuidle are following different path: the cpuidle core
> code goes to linux-pm, the ARM drivers goes to arm-soc or the SoC specific
> tree, sh goes through sh arch tree, pseries goes through PowerPC and
> finally intel goes through Len's tree while acpi_idle goes under linux-pm.
>
> That makes difficult to consolidate the code and to propagate modifications
> from the cpuidle core to the different drivers.
>
> Hopefully, a movement has initiated to put the cpuidle drivers into the
> drivers/cpuidle directory like cpuidle-calxeda.c and cpuidle-kirkwood.c
>
> Add an explicit maintainer entry in the MAINTAINER to clarify the situation
> and prevent new cpuidle drivers to goes to an arch directory.
>
> The upstreaming process is unchanged: Rafael takes the patches to merge them
> into its tree but with the acked-by from the driver's maintainer. So the header
> must contains the name of the maintainer.
>
> This organization will be the same than cpufreq.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> Acked-by: Andrew Lunn <andrew@lunn.ch> #for kirkwood
> Acked-by: Jason Cooper <jason@lakedaemon.net> #for kirkwood
Acked-by: Kevin Hilman <khilman@linaro.org>
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [V2 PATCH] cpuidle: add maintainer entry
Date: Fri, 26 Apr 2013 09:49:46 -0700 [thread overview]
Message-ID: <87txmtz179.fsf@linaro.org> (raw)
In-Reply-To: <1366974344-26064-1-git-send-email-daniel.lezcano@linaro.org> (Daniel Lezcano's message of "Fri, 26 Apr 2013 13:05:44 +0200")
Daniel Lezcano <daniel.lezcano@linaro.org> writes:
> Currently the cpuidle drivers are spread across the different archs.
>
> The patch submission for cpuidle are following different path: the cpuidle core
> code goes to linux-pm, the ARM drivers goes to arm-soc or the SoC specific
> tree, sh goes through sh arch tree, pseries goes through PowerPC and
> finally intel goes through Len's tree while acpi_idle goes under linux-pm.
>
> That makes difficult to consolidate the code and to propagate modifications
> from the cpuidle core to the different drivers.
>
> Hopefully, a movement has initiated to put the cpuidle drivers into the
> drivers/cpuidle directory like cpuidle-calxeda.c and cpuidle-kirkwood.c
>
> Add an explicit maintainer entry in the MAINTAINER to clarify the situation
> and prevent new cpuidle drivers to goes to an arch directory.
>
> The upstreaming process is unchanged: Rafael takes the patches to merge them
> into its tree but with the acked-by from the driver's maintainer. So the header
> must contains the name of the maintainer.
>
> This organization will be the same than cpufreq.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> Acked-by: Andrew Lunn <andrew@lunn.ch> #for kirkwood
> Acked-by: Jason Cooper <jason@lakedaemon.net> #for kirkwood
Acked-by: Kevin Hilman <khilman@linaro.org>
next prev parent reply other threads:[~2013-04-26 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 11:05 [V2 PATCH] cpuidle: add maintainer entry Daniel Lezcano
2013-04-26 11:05 ` Daniel Lezcano
2013-04-26 12:05 ` Rafael J. Wysocki
2013-04-26 12:05 ` Rafael J. Wysocki
2013-04-26 16:49 ` Kevin Hilman [this message]
2013-04-26 16:49 ` Kevin Hilman
2013-04-26 17:01 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-26 17:01 ` Jean-Christophe PLAGNIOL-VILLARD
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=87txmtz179.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=benh@kernel.crashing.org \
--cc=daniel.lezcano@linaro.org \
--cc=horms+renesas@verge.net.au \
--cc=horms@verge.net.au \
--cc=jason@lakedaemon.net \
--cc=josephl@nvidia.com \
--cc=kernel@pengutronix.de \
--cc=kgene.kim@samsung.com \
--cc=lenb@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=magnus.damm@gmail.com \
--cc=nicolas.ferre@atmel.com \
--cc=nsekhar@ti.com \
--cc=paulus@samba.org \
--cc=plagnioj@jcrosoft.com \
--cc=rjw@sisk.pl \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.