From: Jeff Garzik <jeff@garzik.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Alan Cox <alan@linux.intel.com>,
linux-kernel@vger.kernel.org, stable@kernel.org,
"Alexandros C. Couloumbis" <alex@ozo.com>,
linux-ide@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [PATCH] pata_sc1200: Fix crash on boot
Date: Wed, 14 Oct 2009 08:52:11 -0400 [thread overview]
Message-ID: <4AD5C97B.4080509@garzik.org> (raw)
In-Reply-To: <200910141412.29467.bzolnier@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
On 10/14/2009 08:12 AM, Bartlomiej Zolnierkiewicz wrote:
> On Wednesday 14 October 2009 14:00:46 Alan Cox wrote:
>>> This patch applies to 2.6.31 and 2.6.30 (at least). How far back
>>> should it be ported?
>>
>> No idea. I was just getting it fixed for the maintainer while waiting for
>> something else to build.
>
> BTW do you happen to know who is the current maintainer of this driver
> (ditto for other PATA drivers)?
>
> MAINTAINERS lists only:
>
> SERIAL ATA (SATA) SUBSYSTEM
> P: Jeff Garzik
> M: jgarzik@pobox.com
> L: linux-ide@vger.kernel.org
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
> S: Supported
> F: drivers/ata/
> F: include/linux/ata.h
> F: include/linux/libata.h
>
> but this driver surely ain't SATA.
FWIW, I've been treating Alan as "PATA sub-maintainer", and tend to wait
for an Alan review of a PATA driver patch before applying it [unless
it's blindingly obvious or Bart chimes etc.].
But yes, overall, libata is certainly not SATA-only anymore, and
MAINTAINERS should reflect that.
Maybe a patch like the attached? (DaveM CC'd, since I modified the
old-IDE entry as well)
Jeff
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 691 bytes --]
diff --git a/MAINTAINERS b/MAINTAINERS
index 69e31aa..1a756bd 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2581,7 +2581,7 @@ W: http://www.developer.ibm.com/welcome/netfinity/serveraid.html
S: Supported
F: drivers/scsi/ips.*
-IDE SUBSYSTEM
+Old IDE SUBSYSTEM
M: "David S. Miller" <davem@davemloft.net>
L: linux-ide@vger.kernel.org
T: git git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide-2.6.git
@@ -4644,7 +4644,7 @@ S: Maintained
F: drivers/misc/phantom.c
F: include/linux/phantom.h
-SERIAL ATA (SATA) SUBSYSTEM
+ATA SUBSYSTEM
M: Jeff Garzik <jgarzik@pobox.com>
L: linux-ide@vger.kernel.org
T: git git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
next prev parent reply other threads:[~2009-10-14 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091006150737.9610.81541.stgit@localhost.localdomain>
2009-10-14 1:56 ` [PATCH] pata_sc1200: Fix crash on boot Andrew Morton
2009-10-14 3:07 ` Alexandros C. Couloumbis
2009-10-14 12:00 ` Alan Cox
2009-10-14 12:12 ` Bartlomiej Zolnierkiewicz
2009-10-14 12:25 ` Alan Cox
2009-10-14 12:52 ` Jeff Garzik [this message]
2009-10-14 12:38 ` Alan Cox
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=4AD5C97B.4080509@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alex@ozo.com \
--cc=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).