cpuidle: add maintainer entry
authorDaniel Lezcano <daniel.lezcano@linaro.org>
Fri, 26 Apr 2013 11:05:44 +0000 (11:05 +0000)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Fri, 26 Apr 2013 20:30:25 +0000 (22:30 +0200)
commita8e39c35b5d09598e129aa9b5e6f35aa3a1915d9
treee5d3a77b0e713e6935badff34c3a789b3ed20be9
parent9fe3d35a32a9be259435e30fdca680cb78bd6d6f
cpuidle: add maintainer entry

Currently cpuidle drivers are spread across different archs.

As a result, there are several different paths for cpuidle patch
submissions: cpuidle core changes go through linux-pm, ARM driver
changes go to the arm-soc or SoC-specific trees, sh changes go
through the sh arch tree, pseries changes go through the PowerPC tree
and finally intel changes go through the Len's tree while ACPI idle
changes go through linux-pm.

That makes it difficult to consolidate code and to propagate
modifications from the cpuidle core to the different drivers.

Hopefully, a movement has started to put the majority of cpuidle
drivers under drivers/cpuidle like cpuidle-calxeda.c and
cpuidle-kirkwood.c.

Add a maintainer entry for cpuidle to MAINTAINERS to clarify the
situation and to indicate to new cpuidle driver authors that those
drivers should not go into arch-specific directories.

The upstreaming process is unchanged: Rafael takes patches for
merging into his tree, but with an Acked-by: tag from the driver's
maintainer, so indicate in the drivers' headers who maintains them.

The arrangement will be the same as for cpufreq.

[rjw: Changelog]
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>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
MAINTAINERS
drivers/cpuidle/cpuidle-calxeda.c
drivers/cpuidle/cpuidle-kirkwood.c