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]>
diff --git a/MAINTAINERS b/MAINTAINERS
index b81b261..fe89a16 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -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
On Fri, 2012-05-04 at 12:04 -0400, Dave Jones wrote:
> 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]>
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b81b261..fe89a16 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -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
If there's no maintainer, it's not really maintained.
Maybe:
S: Orphan
Hi Dave,
On Friday, May 04, 2012, Dave Jones wrote:
> 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]>
Would you mind if I took over the maintenance of cpufreq, so that it goes
along with the other core power management code?
Rafael
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b81b261..fe89a16 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -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/
>
>
On Saturday, May 05, 2012, Rafael J. Wysocki wrote:
> Hi Dave,
>
> On Friday, May 04, 2012, Dave Jones wrote:
> > 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]>
>
> 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". :-)
Thanks,
Rafael
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index b81b261..fe89a16 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -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/
> >
> >
>
> --
> 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
>
>
On Fri, May 11, 2012 at 09:16:25PM +0200, Rafael J. Wysocki wrote:
> On Saturday, May 05, 2012, Rafael J. Wysocki wrote:
> > Hi Dave,
> >
> > On Friday, May 04, 2012, Dave Jones wrote:
> > > 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]>
> >
> > 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.
Dave
On Friday, May 11, 2012, Dave Jones wrote:
> On Fri, May 11, 2012 at 09:16:25PM +0200, Rafael J. Wysocki wrote:
> > On Saturday, May 05, 2012, Rafael J. Wysocki wrote:
> > > Hi Dave,
> > >
> > > On Friday, May 04, 2012, Dave Jones wrote:
> > > > 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]>
> > >
> > > 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.
Cool, thanks!
> 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.
Sure.
> 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.
I agree.
Thanks a lot,
Rafael
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.
Signed-off-by: Rafael J. Wysocki <[email protected]>
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
Index: linux/MAINTAINERS
===================================================================
--- linux.orig/MAINTAINERS
+++ linux/MAINTAINERS
@@ -1970,7 +1970,9 @@ S: Maintained
F: drivers/net/ethernet/ti/cpmac.c
CPU FREQUENCY DRIVERS
+M: Rafael J. Wysocki <[email protected]>
L: [email protected]
+L: [email protected]
S: Maintained
F: drivers/cpufreq/
F: include/linux/cpufreq.h
Hi Rafael, Dave,
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
--
Cheers,
Stephen Rothwell [email protected]
Hi Stephen,
On Sunday, May 13, 2012, Stephen Rothwell wrote:
> Hi Rafael, Dave,
>
> 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
I will push future cpufreq updates through the linux-pm tree.
Thanks,
Rafael
Hi Rafael,
On Sun, 13 May 2012 15:12:36 +0200 "Rafael J. Wysocki" <[email protected]> wrote:
>
> On Sunday, May 13, 2012, Stephen Rothwell wrote:
> >
> > 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
>
> I will push future cpufreq updates through the linux-pm tree.
OK, I will remove the two trees above from linux-next.
--
Cheers,
Stephen Rothwell [email protected]