public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Cromie <jim.cromie@gmail.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	Christer Weinigel <christer@weinigel.se>
Subject: Re: [patch 2.6.18+] MAINTAINERS - take over scx200-* and pc8736* drivers
Date: Thu, 05 Oct 2006 07:22:21 -0600	[thread overview]
Message-ID: <4525070D.9030609@gmail.com> (raw)
In-Reply-To: <20061005105351.f791f4f1.khali@linux-fr.org>


Add MAINTAINERS entries for new scx200_hrt and pc8736x_gpio drivers, and 
take over maintenance of scx200_gpio, authored by Christer Weinigel 
(which Ive hacked at), who no longer has the hardware.
Also take over hwmon/pc87360, authored by Jean Delvare, who's dropped 
maintenance to dedicate more time to hwmon subsystem.


Signed-off-by:  Jim Cromie <jim.cromie@gmail.com>
---

Christer acked this off-list already, in case he's too busy and misses 
this one.

$ diffstat diff.maintainers
 MAINTAINERS |   28 ++++++++++++++++++++++++----
 1 files changed, 24 insertions(+), 4 deletions(-)



Jean Delvare wrote:
> Yep, I'm fine with Jim taking over maintainerchip of the pc87360
> hardware monitoring driver.
>
>   

>> +NSC_GPIO Common Methods Module (supports PC8736x_GPIO and SCX200_GPIO Drivers)
>>     
>
> All other entries in this file are uppercase.
>
> I also doubt that anyone will ever search for "common methods module",
> I'm not even sure I understand what it means. What's really important
> here are the driver names IMHO, and you already have added entries for
> these below - isn't that sufficient?
>
>   
Ack.  I was ambivalent about this, since its not a driver, and nobody 
would modprobe it directly.
I went for thoroughness, assuming Id be corrected.. ;-)


diff -ruNp -X dontdiff -X exclude-diffs linux-2.6.18/MAINTAINERS doc-touches/MAINTAINERS
--- linux-2.6.18/MAINTAINERS	2006-09-19 23:57:12.000000000 -0600
+++ doc-touches/MAINTAINERS	2006-10-05 07:03:45.000000000 -0600
@@ -2215,6 +2215,17 @@ T:	git kernel.org:/pub/scm/linux/kernel/
 T:	cvs cvs.parisc-linux.org:/var/cvs/linux-2.6
 S:	Maintained
 
+PC87360 HARDWARE MONITORING DRIVER
+P:	Jim Cromie
+M:	jim.cromie@gmail.com
+L:	lm-sensors@lm-sensors.org
+S:	Maintained
+
+PC8736x GPIO DRIVER
+P:	Jim Cromie
+M:	jim.cromie@gmail.com
+S:	Maintained
+
 PCI ERROR RECOVERY
 P:	Linas Vepstas
 M:	linas@austin.ibm.com
@@ -2525,10 +2536,19 @@ L: lksctp-developers@lists.sourceforge.n
 S: Supported
 
 SCx200 CPU SUPPORT
-P:	Christer Weinigel
-M:	christer@weinigel.se
-W:	http://www.weinigel.se
-S:	Supported
+P:	Jim Cromie
+M:	jim.cromie@gmail.com
+S:	Odd Fixes
+
+SCx200 GPIO DRIVER
+P:	Jim Cromie
+M:	jim.cromie@gmail.com
+S:	Maintained
+
+SCx200 HRT CLOCKSOURCE DRIVER
+P:	Jim Cromie
+M:	jim.cromie@gmail.com
+S:	Maintained
 
 SECURITY CONTACT
 P:	Security Officers



      reply	other threads:[~2006-10-05 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05  4:21 [patch 2.6.18+] MAINTAINERS - take over scx200-* and pc8736* drivers Jim Cromie
2006-10-05  8:53 ` Jean Delvare
2006-10-05 13:22   ` Jim Cromie [this message]

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=4525070D.9030609@gmail.com \
    --to=jim.cromie@gmail.com \
    --cc=akpm@osdl.org \
    --cc=christer@weinigel.se \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.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