All of lore.kernel.org
 help / color / mirror / Atom feed
From: Divy Le Ray <divy@chelsio.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Steve Wise <swise@opengridcomputing.com>
Subject: [PATCH 0/11] cxgb3 - driver updates
Date: Tue, 21 Aug 2007 20:45:04 -0700	[thread overview]
Message-ID: <46CBB140.7060501@chelsio.com> (raw)

Jeff,

I'm resubmitting the last cxgb3 patch series against netdev-2.6#upstream,
minus the first patch that you already applied and the last patch.

Here is a brief description:
-       Modify max HW Rx coalescing size
-       Log SGE doorbell Fifo overflow
-       Use Tx immediate data for offload packets whenever possible
-       RDMA can get internal mem info to workaround HW issues
-       More validity checks on connection ids
-       Stop MAC when a fatal error is detected
-       Log HW serial number
-       Update internal mem operating mode
-       Update engine microcode management, version is now 1.1.0
-       Update FW management, version is now 4.6.0
-       Ignore some HW errors until the HW is initialized

Cheers,
Divy




                 reply	other threads:[~2007-08-22  3:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=46CBB140.7060501@chelsio.com \
    --to=divy@chelsio.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=swise@opengridcomputing.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 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.