From: Divy Le Ray <divy@chelsio.com>
To: Jeff Garzik <jeff@garzik.org>, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Steve Wise <swise@opengridcomputing.com>,
David Miller <davem@davemloft.net>
Subject: [PATCH 0/8 2.6.28] cxgb3 - driver update
Date: Wed, 08 Oct 2008 17:32:40 -0700 [thread overview]
Message-ID: <48ED5128.4070004@chelsio.com> (raw)
[cc-ing Dave in Jeff's absence]
Hi Jeff,
I'm submitting 8 update patches against net-next-2.6 for inclusion in
2.6.28.
Here is a brief description of the patch series:
- reset the chip and bring ports back up when a fatal error occurs
- set multiple queues per default in MSI-X mode
[the following patches re-organize the PHY related code,
and add more PHYs support]
- account for phy reset errors
- simplify PHY related structures
- add flexibility in PHY interrupt support
- introduce generic code for PHY interrupt support
- add support for Aeluros 2005 PHY
- add support for optical Vitess 8211 phy.
Cheers,
Divy
reply other threads:[~2008-10-09 0:32 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=48ED5128.4070004@chelsio.com \
--to=divy@chelsio.com \
--cc=davem@davemloft.net \
--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 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).