mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Dave Jones <davej@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: CPU frequency drivers MAINTAINERS update
Date: Fri, 11 May 2012 21:34:02 +0200	[thread overview]
Message-ID: <201205112134.02273.rjw@sisk.pl> (raw)
In-Reply-To: <20120511192420.GA10041@redhat.com>

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 <davej@redhat.com>
>  > > 
>  > > 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

  reply	other threads:[~2012-05-11 19:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 16:04 Dave Jones
2012-05-04 16:50 ` Joe Perches
2012-05-05 19:10 ` Rafael J. Wysocki
2012-05-11 19:16   ` Rafael J. Wysocki
2012-05-11 19:24     ` Dave Jones
2012-05-11 19:34       ` Rafael J. Wysocki [this message]
2012-05-11 19:35       ` [PATCH] MAINTAINERS: Add myself as the cpufreq maintainer Rafael J. Wysocki
2012-05-13  0:19         ` Stephen Rothwell
2012-05-13 13:12           ` Rafael J. Wysocki
2012-05-13 14:03             ` Stephen Rothwell

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=201205112134.02273.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®