From: Jeff Garzik <jeff@garzik.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [rft] r8169: merge release 6.001.00 of Realtek's driver - take #1
Date: Fri, 26 Jan 2007 03:35:12 -0500 [thread overview]
Message-ID: <45B9BD40.4000708@garzik.org> (raw)
In-Reply-To: <20070124231719.GA10010@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Untested, straight from the "release early" dept. You have been warned.
>
> Realtek's driver restricts itself to 0x8169 and 0x8167.
> It won't be surprising if it breaks on anything else until
> I merge the new 0x8168 and 0x8136 bits.
>
> Signed-off-by: Francois Romieu <romieu@fr.zoreil.com>
FWIW I would like to see if we can train RealTek to directly submit
kernel patches, and try to mentor them into helping you maintain the
RealTek stuff.
Jeff
prev parent reply other threads:[~2007-01-26 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 23:17 [rft] r8169: merge release 6.001.00 of Realtek's driver - take #1 Francois Romieu
2007-01-26 8:13 ` Bernhard Walle
2007-01-26 8:35 ` Jeff Garzik [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=45B9BD40.4000708@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--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).