From: Xose Vazquez Perez <xose@wanadoo.es>
To: "David S. Miller" <davem@redhat.com>
Cc: jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: [PATCH] tg3, more IDs
Date: Tue, 09 Dec 2003 18:23:14 +0100 [thread overview]
Message-ID: <3FD60502.5050300@wanadoo.es> (raw)
In-Reply-To: 20031208215657.550ba7e0.davem@redhat.com
David S. Miller wrote:
> Applied, but please next time remember to edit drivers/pci/pci.ids
> as well when adding new PCI device ids.
I usually send pci.ids updates to pciids.sf.net
Today it contains a _kilopatch_ of new entries, more than kernel_pci.ids
I was speaking with Martin Mares weeks ago to try that he did a 'commit'.
I don't know what happens with him. Does anyone know anything?
There are more pciids developers:
Dave Jones
Arjan van de Ven
Jeff Garzik
Lenz Grimmer
Martin Mares
Mike A. Harris
Bill Nottingham
Vojtech Pavlik
but until now, nobody cares about it.
Next time I will send it to you.
-thanks-
prev parent reply other threads:[~2003-12-09 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 16:49 [PATCH] tg3, more IDs Xose Vazquez Perez
2003-12-06 18:03 ` Xose Vazquez Perez
2003-12-09 5:56 ` David S. Miller
2003-12-09 17:23 ` Xose Vazquez Perez [this message]
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=3FD60502.5050300@wanadoo.es \
--to=xose@wanadoo.es \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
/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).