netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Linsys Contractor Mithlesh Thukral <mithlesh@netxen.com>
Cc: netdev@vger.kernel.org, amitkale@netxen.com,
	netxenproj@linsyssoft.com, rob@netxen.com
Subject: Re: [PATCH 0/5] NetXen: Driver bug fixes
Date: Fri, 09 Mar 2007 11:56:19 -0500	[thread overview]
Message-ID: <45F191B3.8090609@garzik.org> (raw)
In-Reply-To: <200703090805.l29855n5011673@dut39.unminc.com>

Linsys Contractor Mithlesh Thukral wrote:
> Hi All,
> 
> I will be sending updates to NetXen: 1G/10G Ethernet driver in subsequent mails.
> The patches will be with respect to netdev#upstream.

Are you sure you don't want some of these in #upstream-fixes, queued for 
2.6.21-rc?

	Jeff




  reply	other threads:[~2007-03-09 16:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09  8:05 [PATCH 0/5] NetXen: Driver bug fixes Linsys Contractor Mithlesh Thukral
2007-03-09 16:56 ` Jeff Garzik [this message]
2007-03-10  7:09   ` Amit Kale
2007-03-10 11:22     ` Jeff Garzik
2007-03-12  6:16       ` Amit Kale
2007-03-12 14:31         ` Jeff Garzik
2007-03-13  5:21           ` Amit Kale

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=45F191B3.8090609@garzik.org \
    --to=jeff@garzik.org \
    --cc=amitkale@netxen.com \
    --cc=mithlesh@netxen.com \
    --cc=netdev@vger.kernel.org \
    --cc=netxenproj@linsyssoft.com \
    --cc=rob@netxen.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).