From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Jens Axboe <axboe@suse.de>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pcmcia: add another ide-cs CF card id
Date: Thu, 2 Mar 2006 12:24:09 +0000 [thread overview]
Message-ID: <20060302122409.GD14017@flint.arm.linux.org.uk> (raw)
In-Reply-To: <4406E1C7.7020908@pobox.com>
On Thu, Mar 02, 2006 at 07:15:03AM -0500, Jeff Garzik wrote:
> Arjan van de Ven wrote:
> >Sure I can it being nice to CC linux-ide ANYWAY, but, to be honest,
> >while I see that is important for changes to the driver that change the
> >structure of it and how it interacts with the IDE layer, I fail to see
> >the hard required reason for that for just adding a *PCMCIA* ID.
> >
> >I think Jeff is a bit overreacting in this case.
>
> About a quarter of the time when non-netdev maintainers add IDs, through
> the magic of merges, we've wound up with duplicate IDs in the driver.
> I've snipped several duplicate IDs from tulip and other net drivers over
> the years.
>
> Further, in the past Brodo has _already_ been asked to CC relevant
> maintainers and lists -- or at least LKML -- with his patches. He has
> established a pattern of lacking time to add CC's to his emails; it
> wasn't just this incident.
>
> Where is the peer review?
I think it's fairly safe and obvious to say that Dominik is the peer
review for these tables - he _is_ the PCMCIA maintainer, he _is_
arguably the maintainer for the ide-cs driver, he _is_ the person
who invented these tables, he _is_ the one taking patches from people
to add IDs, he _is_ the one reviewing such patches.
If you want to know what's going on in PCMCIA land, subscribe to
linux-pcmcia. In the same way that if you want to know what's going
in in IDE land, you subscribe to linux-ide, or PCI land linux-pci,
SCSI land linux-scsi, network land netdev.
Using your argument (which seems to be demanding that any patch to
any IDE driver no matter how trivial must be on linux-ide) that a patch
to a PCI network device driver must be copied to linux-pci and netdev
even though it may not touch the PCI specific code.
What about a cardbus network card? Should any patch no matter how
trivial be sent to netdev, linux-pci and linux-pcmcia - all those three
mailing lists are within the "sphere of influence" of any patch to that
driver.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-03-02 12:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200603012259.k21MxBXC013582@hera.kernel.org>
2006-03-01 23:36 ` [PATCH] pcmcia: add another ide-cs CF card id Jeff Garzik
[not found] ` <20060302075004.GA17789@isilmar.linta.de>
2006-03-02 11:17 ` Jeff Garzik
2006-03-02 11:31 ` Arjan van de Ven
2006-03-02 11:42 ` Jens Axboe
2006-03-02 11:56 ` Arjan van de Ven
2006-03-02 12:07 ` Arjan van de Ven
2006-03-02 12:15 ` Jeff Garzik
2006-03-02 12:24 ` Russell King [this message]
2006-03-02 12:38 ` Jeff Garzik
2006-03-02 13:02 ` Arjan van de Ven
2006-03-02 12:27 ` Arjan van de Ven
2006-03-02 12:40 ` Jeff Garzik
2006-03-02 13:00 ` Dominik Brodowski
2006-03-02 13:06 ` Jeff Garzik
2006-03-02 11:44 ` Jeff Garzik
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=20060302122409.GD14017@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=arjan@infradead.org \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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