mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Dave Jones <davej@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: CPU frequency drivers MAINTAINERS update
Date: Fri, 04 May 2012 09:50:41 -0700	[thread overview]
Message-ID: <1336150241.7920.17.camel@joe2Laptop> (raw)
In-Reply-To: <20120504160417.GA421@redhat.com>

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 <davej@redhat.com>
> 
> 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 <davej@redhat.com>
>  L:	cpufreq@vger.kernel.org
> -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



  reply	other threads:[~2012-05-04 16:50 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 [this message]
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
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=1336150241.7920.17.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@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®