From: "David S. Miller" <davem@redhat.com>
To: Xose Vazquez Perez <xose@wanadoo.es>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6] pci.ids for e1000
Date: Mon, 29 Sep 2003 23:25:20 -0700 [thread overview]
Message-ID: <20030929232520.0184a8f7.davem@redhat.com> (raw)
In-Reply-To: <3F621965.4070106@wanadoo.es>
On Fri, 12 Sep 2003 21:07:17 +0200
Xose Vazquez Perez <xose@wanadoo.es> wrote:
> Linus and Marcelo should not accept patches against pci.ids,
> all updates should go to pciids.sf.net. And every X time
> to do a sync with 2.4 and 2.6.
I don't know if this is the best idea.
When merging in a driver, it makes perfect sense to add the
appropriate device IDs to all PCI ID files.
On the other hand this could make life difficult for the
pciids.sf.net person.
next prev parent reply other threads:[~2003-09-30 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 19:07 [PATCH 2.6] pci.ids for e1000 Xose Vazquez Perez
2003-09-30 6:25 ` David S. Miller [this message]
2003-09-30 23:32 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 20:15 Xose Vazquez Perez
2003-09-12 18:40 Feldman, Scott
2003-09-12 1:11 Feldman, Scott
2003-09-12 16:08 ` 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=20030929232520.0184a8f7.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=xose@wanadoo.es \
/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.