netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev ML <netdev@vger.kernel.org>
Subject: Re: [RFT] r8169 changes against 2.6.23-rc3
Date: Mon, 20 Aug 2007 14:58:05 -0400	[thread overview]
Message-ID: <46C9E43D.4050306@oracle.com> (raw)
In-Reply-To: <20070818100701.GA20703@electric-eye.fr.zoreil.com>

[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]

Francois Romieu wrote:
> The latest serie of r8169 changes is available against 2.6.23-rc3 as:
> http://www.fr.zoreil.com/people/francois/misc/20070818-2.6.23-rc3-r8169-test.patch 
> 
> or (tarball sits one level higher):
> 
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.23-rc3/r8169-20070818/
> 
> or (rebase prone branch)
> 
> git://electric-eye.fr.zoreil.com/home/romieu/linux-2.6.git#r8169
>  
> Please do not clone your whole git kernel tree from here, thanks.
> 
> Changes (most recent first):
> 
> - eeprom read support
> - phy init cleanup
> - PHY init for the 8168
> - make room for more PHY init changes
> - remove dead wood
> - add MAC identifiers
> - MSI support
> - correct phy parameters for the 8110SC
> 
> The first patch of the serie ("correct phy parameters for the 8110SC") has
> been elaborated with Edward Hsu from Realtek and it should help some owners
> of 8169 chipsets. If there is no report of regression for it on any
> chispet and it is reported to fix someone's problems, I will send it to
> Jeff Garzik for inclusion in 2.6.23 as a bugfix.
> 
> Anything else in this serie has not been tested on a wide scale nor acked
> by the manufacturer: I consider it post 2.6.23 material. That being said,
> the MSI changes seem fine and the "PHY init for the 8168" patch could make
> a difference for the users of the 8168 whose link is not properly
> negotiated.
> 
> Success and failure reports or patches will be welcome. Please Cc: netdev
> and include "r8169" in the Subject.

Tested 2.6.23-rc3 plus your patch on my dual-R8169 mini-ITX Jetway 
J7F4K1G2E mainboard.  No problems to report.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard


  parent reply	other threads:[~2007-08-20 18:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070818100701.GA20703@electric-eye.fr.zoreil.com>
2007-08-19  2:41 ` [RFT] r8169 changes against 2.6.23-rc3 Bruce Cole
2007-08-20  8:34   ` Dirk
2007-08-20 18:58 ` Chuck Lever [this message]
2007-08-21 19:32 Bruce Cole
2007-08-22  5:51 ` Bruce Cole

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=46C9E43D.4050306@oracle.com \
    --to=chuck.lever@oracle.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).