From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Realtek linux nic maintainers <nic_swsd@realtek.com>,
Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: Add support for D-Link 530T rev C1 (Kernel Bug 38862)
Date: Thu, 28 Jul 2011 19:35:35 -0400 [thread overview]
Message-ID: <20110728233535.GA8566@caffeine.csclub.uwaterloo.ca> (raw)
In-Reply-To: <20110728163434.4d3bb048@nehalam.ftrdhcpuser.net>
On Thu, Jul 28, 2011 at 04:34:34PM -0700, Stephen Hemminger wrote:
> Glad they at least changed the PCI-ID this time.
> Other vendors have been known to do it wrong.
No kidding. Ick.
--
Len Sorensen
prev parent reply other threads:[~2011-07-28 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 23:18 Add support for D-Link 530T rev C1 (Kernel Bug 38862) Lennart Sorensen
2011-07-28 23:34 ` Stephen Hemminger
2011-07-28 23:35 ` Lennart Sorensen [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=20110728233535.GA8566@caffeine.csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=romieu@fr.zoreil.com \
--cc=shemminger@vyatta.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).