From: Jeff Garzik <jgarzik@pobox.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ethtool: new ID to decode the registers of the 8168 (realtek)
Date: Thu, 24 May 2007 17:50:02 -0400 [thread overview]
Message-ID: <4656088A.6030006@pobox.com> (raw)
In-Reply-To: <20070524200242.GA17722@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Tested with an Asrock 945G-DVI (LOM).
>
> Signed-off-by: Francois Romieu <romieu@fr.zoreil.com>
> ---
> realtek.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
applied
Also, I have really fallen off the ball when it comes to the r8169
kernel driver. My apologies.
Would you be kind enough to resend? If there are important bug fixes
that need to go into 2.6.22, that are safe enough to put in at this late
date, please split those off from other improvements.
Jeff
next prev parent reply other threads:[~2007-05-24 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 20:02 [PATCH] ethtool: new ID to decode the registers of the 8168 (realtek) Francois Romieu
2007-05-24 21:50 ` Jeff Garzik [this message]
2007-05-24 22:57 ` Francois Romieu
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=4656088A.6030006@pobox.com \
--to=jgarzik@pobox.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).