All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: "Garzik, Jeff" <jgarzik@pobox.com>,
	netdev@vger.kernel.org, "Brandeburg,
	Jesse" <jesse.brandeburg@intel.com>,
	"Kok, Auke" <auke@foo-projects.org>,
	"Ronciak, John" <john.ronciak@intel.com>
Subject: Re: [PATCH 2.4 0/3] e1000: update to 7.3.20
Date: Tue, 6 Feb 2007 12:29:57 +0100	[thread overview]
Message-ID: <20070206112957.GA5087@1wt.eu> (raw)
In-Reply-To: <20070206010102.28691.96744.stgit@gitlost.site>

Hi Auke,

On Mon, Feb 05, 2007 at 05:01:02PM -0800, Kok, Auke wrote:
> Willy,
> 
> Please pull:
> 
> git-pull git://lost.foo-projects.org/~ahkok/git/linux-2.4 e1000
> 
> to receive an update for the e1000 driver. This updates the e1000
> driver in the 2.4 kernel to version 7.3.20-k4, roughly the equivalent
> of what is in 2.6.20 and the latest of our out-of-tree driver.
> 
> This adds new hardware support and many fixes. Many customers are
> asking us for these updates and the current 2.4 kernel ships a very
> outdated version of the e1000 adapter.
> 
> This patch includes small compatibility headers and code to minimize
> the changes we need to make to our driver and keep it in sync easier
> with the 2.6 kernel version so we can possibly continue to ship
> updates and fixes to this driver with more ease.

Pulled, thanks very much. I'll produce -pre1 shortly so that we can
ensure there's no regression.

> Cheers,
> 
> Auke

Best Regards,
Willy


      parent reply	other threads:[~2007-02-06 11:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-06  1:01 [PATCH 2.4 0/3] e1000: update to 7.3.20 Kok, Auke
2007-02-06  1:01 ` [PATCH 2/3] [MAINTAINERS]: update e1000 maintainers Kok, Auke
2007-02-06  1:01 ` [PATCH 3/3] e1000: update README Kok, Auke
2007-02-06 11:29 ` Willy Tarreau [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=20070206112957.GA5087@1wt.eu \
    --to=w@1wt.eu \
    --cc=auke-jan.h.kok@intel.com \
    --cc=auke@foo-projects.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=john.ronciak@intel.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.