From: Jeff Garzik <jgarzik@pobox.com>
To: Xose Vazquez Perez <xose@wanadoo.es>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH ] more eepro100 boards
Date: Wed, 19 Nov 2003 12:18:57 -0500 [thread overview]
Message-ID: <3FBBA601.3080709@pobox.com> (raw)
In-Reply-To: <3FBA97E4.1060004@wanadoo.es>
Xose Vazquez Perez wrote:
> deleted PCI_DEVICE_ID_INTEL_82801BA_7, it's a duplicate of 0x2449
>
> and added five boards:
>
> 0x1051
> 0x1052
> 0x1053
> 0x1054
> 0x1055
>
>
> These should be deleted:
>
> 0x1035
> 0x1036
> 0x1037
> 0x1227
> 0x1228
> 0x5200
> 0x5201
>
> Time ago, in conversation with some intel guys, they said me that
> those boards are not compatibles with the driver. Do anyone run
> eepro100 with any of those boards?
Indeed.... I would like to delay this patch, until we are confirmed
that these pci ids do indeed work with eepro100.c. Once we get
confirmation, I am OK with applying.
Jeff
next prev parent reply other threads:[~2003-11-19 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 22:06 [PATCH ] more eepro100 boards Xose Vazquez Perez
2003-11-19 17:18 ` Jeff Garzik [this message]
2005-02-01 20:17 ` [ PATCH ] 2.6 eepro100: replace and delete duplicate ids Xose Vazquez Perez
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=3FBBA601.3080709@pobox.com \
--to=jgarzik@pobox.com \
--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 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).