From: Ben Hutchings <bhutchings@solarflare.com>
To: Peter Wu <lekensteyn@gmail.com>
Cc: <netdev@vger.kernel.org>, Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: [PATCH 2/2] realtek: update devices to 3.11
Date: Thu, 29 Aug 2013 21:52:06 +0100 [thread overview]
Message-ID: <1377809526.5372.18.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <1376429119-31380-3-git-send-email-lekensteyn@gmail.com>
On Tue, 2013-08-13 at 23:25 +0200, Peter Wu wrote:
> RTL8168_8111Bb/RTL8168_8111Bef is like RTL8111B/RTL8168B, RTL8100E and RTL8101E
> (datasheet revision 1.0 from 26 January 2006). Assume that RTL8101e is also
> similar (I may be very wrong at that though...).
>
> Note that the scanning heuristics is the same as the r8169 module: newer devices
> with stronger masks come before the others. Perhaps the older 8139 cards should
> be appended to the list, after all r8169 chips.
>
> Signed-off-by: Peter Wu <lekensteyn@gmail.com>
[...]
Applied, thanks.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2013-08-29 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 21:25 [PATCH v4 ethtool 0/2] Add new Realtek devices Peter Wu
2013-08-13 21:25 ` [PATCH 1/2] realtek: convert to per-chip mask Peter Wu
2013-08-29 20:51 ` Ben Hutchings
2013-08-13 21:25 ` [PATCH 2/2] realtek: update devices to 3.11 Peter Wu
2013-08-29 20:52 ` Ben Hutchings [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-23 8:51 [ethtool] Add new Realtek devices Peter Wu
2013-07-23 8:51 ` [PATCH 2/2] realtek: update devices to 3.11 Peter Wu
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=1377809526.5372.18.camel@bwh-desktop.uk.level5networks.com \
--to=bhutchings@solarflare.com \
--cc=lekensteyn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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).