From: Jeff Garzik <jgarzik@pobox.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
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, 02 Mar 2006 07:38:49 -0500 [thread overview]
Message-ID: <4406E759.2010601@pobox.com> (raw)
In-Reply-To: <20060302122409.GD14017@flint.arm.linux.org.uk>
Russell King wrote:
> 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.
IDE driver -> IDE reviewers
network driver -> network reviewers
The bus associated with the driver is only a tiny detail. Many drivers
(IDE!) are multi-bus, even.
Linus occasionally complains about stuff hiding on non-LKML lists...
Even a CC to LKML would have been sufficient here. That was not done.
Jeff
next prev parent reply other threads:[~2006-03-02 12:39 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
2006-03-02 12:38 ` Jeff Garzik [this message]
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=4406E759.2010601@pobox.com \
--to=jgarzik@pobox.com \
--cc=arjan@infradead.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rmk+lkml@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.