From: Jeff Garzik <jgarzik@pobox.com>
To: sfeldma@pobox.com
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH 2.6] eepro100: remove ID for 82556
Date: Sat, 19 Feb 2005 00:03:31 -0500 [thread overview]
Message-ID: <4216C8A3.4020303@pobox.com> (raw)
In-Reply-To: <1107285106.3366.106.camel@sfeldma-mobl.dsl-verizon.net>
Scott Feldman wrote:
> 82556 support doesn't work with eepro100, so this removes the ID
> (0x1228) for 82556. See this thread for more info:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=110726223221165&w=2
>
> Signed-off-by: Scott Feldman <sfeldma@pobox.com>
I see the thread, but I still worry about removing the id in your patch,
since the poster in the thread says that they had to -add- an ID to both
e100 and eepro100 in order to perform their test.
Has anyone with this PCI ID actually confirmed that eepro100 does not
work for them?
Jeff
next prev parent reply other threads:[~2005-02-19 5:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 19:11 [PATCH 2.6] eepro100: remove ID for 82556 Scott Feldman
2005-02-19 5:03 ` Jeff Garzik [this message]
2005-02-19 8:08 ` Meelis Roos
2005-02-19 18:18 ` John Ronciak
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=4216C8A3.4020303@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=sfeldma@pobox.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).