From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Netdev <netdev@oss.sgi.com>
Subject: Re: [PATCH 2/2] [2.6] update forcedeth from 0.22 to 0.23
Date: Thu, 29 Jan 2004 23:38:15 +0100 [thread overview]
Message-ID: <40198B57.2000305@gmx.net> (raw)
In-Reply-To: <4016499D.6020302@gmx.net>
On On Tue, 27 Jan 2004 I wrote:
> Jeff,
>
> this patch updates forcedeth 0.22 to 0.23. The main changes are:
> - Support ethtool
> - Make the generic function names more descriptive
>
> Please consider applying this patch and the previous one.
>
> The other comments we received during the discussion a few days ago will
> be addressed in later versions. Right now I want to get the driver in a
> state suitable for inclusion in 2.4 to get a wider testing base.
>
> Comments are welcome.
Since I received no comments/criticism at all, I assume everyone thinks
forcedeth 0.23 is suitable for inclusion in 2.4.
If nobody protests, I will send forcedeth 0.23 to Marcelo on Tuesday
February 4th.
Regards,
Carl-Daniel
prev parent reply other threads:[~2004-01-29 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 11:21 [PATCH 2/2] [2.6] update forcedeth from 0.22 to 0.23 Carl-Daniel Hailfinger
2004-01-29 22:38 ` Carl-Daniel Hailfinger [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=40198B57.2000305@gmx.net \
--to=c-d.hailfinger.kernel.2004@gmx.net \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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).