CPU frequency drivers MAINTAINERS update

Remove myself as cpufreq maintainer.
x86 driver changes can go through the regular x86/ACPI trees. ARM driver changes through the ARM trees.
cpufreq core changes are rare these days, and can just go to lkml/direct.

Signed-off-by Dave Jones <[email protected]>

MAINTAINERS +0 -0

index b81b261..fe89a16 100644

Remove myself as cpufreq maintainer.
x86 driver changes can go through the regular x86/ACPI trees. ARM driver changes through the ARM trees.
cpufreq core changes are rare these days, and can just go to lkml/direct.

Signed-off-by Dave Jones <[email protected]>

MAINTAINERS +0 -4

index b81b261..fe89a16 100644
@@ -1968,10 +1968,7 @@ S:	Maintained
 F:	drivers/net/ethernet/ti/cpmac.c
 
 CPU FREQUENCY DRIVERS
-M:	Dave Jones <[email protected]>
 L:	[email protected]
-W:	http://www.codemonkey.org.uk/projects/cpufreq/
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq.git
 S:	Maintained
 F:	drivers/cpufreq/
 F:	include/linux/cpufreq.h
--

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Hi Dave,

Quoted 5 lines · Dave Jones

Remove myself as cpufreq maintainer.
x86 driver changes can go through the regular x86/ACPI trees. ARM driver changes through the ARM trees.
cpufreq core changes are rare these days, and can just go to lkml/direct.

Quoted 1 line

Signed-off-by Dave Jones <[email protected]>

Would you mind if I took over the maintenance of cpufreq, so that it goes along with the other core power management code?

Quoted 16 lines

MAINTAINERS +0 -4

index b81b261..fe89a16 100644
@@ -1968,10 +1968,7 @@ S:	Maintained
 F:	drivers/net/ethernet/ti/cpmac.c
 
 CPU FREQUENCY DRIVERS
-M:	Dave Jones <[email protected]>
 L:	[email protected]
-W:	http://www.codemonkey.org.uk/projects/cpufreq/
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq.git
 S:	Maintained
 F:	drivers/cpufreq/
 F:	include/linux/cpufreq.h
--

Quoted 6 lines

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

--
To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Quoted 8 lines · Rafael J. Wysocki

Hi Dave,

Quoted 5 lines · Dave Jones

Remove myself as cpufreq maintainer.
x86 driver changes can go through the regular x86/ACPI trees. ARM driver changes through the ARM trees.
cpufreq core changes are rare these days, and can just go to lkml/direct.

Quoted 4 lines

Quoted 1 line

Signed-off-by Dave Jones <[email protected]>

Would you mind if I took over the maintenance of cpufreq, so that it goes along with the other core power management code?

I'm taking the silence as "no, I wouldn't". :-)

Quoted 11 lines · Rafael J. Wysocki

Quoted 10 lines · Rafael J. Wysocki

Hi Dave,

Quoted 6 lines · Dave Jones

Remove myself as cpufreq maintainer.
x86 driver changes can go through the regular x86/ACPI trees. ARM driver changes through the ARM trees.
cpufreq core changes are rare these days, and can just go to lkml/direct.

Signed-off-by Dave Jones <[email protected]>

Quoted 4 lines

Quoted 2 lines

Would you mind if I took over the maintenance of cpufreq, so that it goes along with the other core power management code?

I'm taking the silence as "no, I wouldn't". :-)

Sure. I'll still be looking at it occasionally so I'll be around to ack things if necessary.

I just don't have time to deal with build-testing
architectures I don't care about for eg, and dealing with the inevitable fallout when things break.

The only words of advice I give to you or whoever takes over, is to push back on adding more sysfs knobs to cpufreq. There's no end to what people want to do, and adding "just one more knob" seems to be the default action. It's already gotten out of hand, and more knobs aren't always the right answer.

From: Rafael J. Wysocki <[email protected]>

Since cpufreq has no official maintainer at the moment, I'm willing to maintain it along some other power management core code I've been maintaining already.

Hi Rafael, Dave,

Quoted 6 lines · On Fri, 11 May 2012 21:35:45 +0200 "Rafael J. Wysocki" <[email protected]> wrote:

From: Rafael J. Wysocki <[email protected]>

Since cpufreq has no official maintainer at the moment, I'm willing to maintain it along some other power management core code I've been maintaining already.

I have cpufreq-current and cpufreq trees in linux-next (both currently empty and with Dave as contact). What should I do with them?

cpufreq-current git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq.git#fixes
cpufreq git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq.git#next

Quoted 9 lines · Stephen Rothwell

Quoted 6 lines · On Fri, 11 May 2012 21:35:45 +0200 "Rafael J. Wysocki" <[email protected]> wrote:

From: Rafael J. Wysocki <[email protected]>

Since cpufreq has no official maintainer at the moment, I'm willing to maintain it along some other power management core code I've been maintaining already.

Quoted 5 lines

I have cpufreq-current and cpufreq trees in linux-next (both currently empty and with Dave as contact). What should I do with them?

cpufreq-current git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq.git#fixes
cpufreq git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq.git#next

I will push future cpufreq updates through the linux-pm tree.