From: Chris Snook <csnook@redhat.com>
To: Konstantin Kalin <konstantin.kalin@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NVIDIA Ethernet & invalid MAC
Date: Tue, 16 Oct 2007 12:00:13 -0400 [thread overview]
Message-ID: <4714E00D.2000505@redhat.com> (raw)
In-Reply-To: <4714C66D.4010607@gmail.com>
Konstantin Kalin wrote:
> P.S. It's simple to add DEV_HAS_CORRECT_MACADDR to pci_device_tlb for
> these types of Ethernet. But I think it's not right decision because it
> would break older revisions of these models.
Any reason you can't distinguish based on PCI ID?
-- Chris
next prev parent reply other threads:[~2007-10-16 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 14:10 NVIDIA Ethernet & invalid MAC Konstantin Kalin
2007-10-16 14:43 ` Alan Cox
2007-10-16 15:16 ` Chuck Ebbert
2007-10-16 15:43 ` Alan Cox
2007-10-16 16:00 ` Jeff Garzik
2007-10-16 16:20 ` YOSHIFUJI Hideaki / 吉藤英明
2007-10-16 16:35 ` Konstantin Kalin
2007-10-16 16:41 ` Jeff Garzik
2007-10-16 16:52 ` Konstantin Kalin
2007-10-17 13:08 ` Konstantin Kalin
2007-10-16 16:00 ` Chris Snook [this message]
2007-10-16 16:07 ` 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=4714E00D.2000505@redhat.com \
--to=csnook@redhat.com \
--cc=konstantin.kalin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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