From: Jeff Garzik <jgarzik@pobox.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: 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:40:34 -0500 [thread overview]
Message-ID: <4406E7C2.7050904@pobox.com> (raw)
In-Reply-To: <1141302442.3206.53.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
>>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.
>
>
> sure. But in this case Dominik IS the maintainer
Bus is far less relevant. Should sbus and SoC bus patches skip
subsystem peer review? Of course not. PCMCIA is not a special case here.
>>Further, in the past Brodo has _already_ been asked to CC relevant
>>maintainers and lists -- or at least LKML -- with his patches.
>
>
> he mailed the relevant list, linux-pcmcia ... whats wrong?
linux-pcmcia is not the place to talk about IDE and net driver patches.
Jeff
next prev parent reply other threads:[~2006-03-02 12:40 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
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 [this message]
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=4406E7C2.7050904@pobox.com \
--to=jgarzik@pobox.com \
--cc=arjan@infradead.org \
--cc=axboe@suse.de \
--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 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.