From: Dhananjay Phadke <dhananjay@netxen.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH NEXT 0/7] netxen: changes for future chip revisions
Date: Thu, 15 Oct 2009 23:09:06 -0700 [thread overview]
Message-ID: <1255673353-31797-1-git-send-email-dhananjay@netxen.com> (raw)
A 7 patch series to add initial support for next
chip chip revision.
Please apply to net-next-2.6 tree.
Thanks,
Dhananjay
next reply other threads:[~2009-10-16 6:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 6:09 Dhananjay Phadke [this message]
2009-10-16 6:09 ` [PATCH NEXT 1/7] netxen; update version to 4.0.56 Dhananjay Phadke
2009-10-17 0:56 ` David Miller
2009-10-17 1:15 ` Dhananjay Phadke
2009-10-16 6:09 ` [PATCH NEXT 2/7] netxen: defines for next revision Dhananjay Phadke
2009-10-16 6:09 ` [PATCH NEXT 3/7] netxen: 128 memory controller support Dhananjay Phadke
2009-10-16 6:09 ` [PATCH NEXT 4/7] netxen: reset sequence changes Dhananjay Phadke
2009-10-16 6:09 ` [PATCH NEXT 5/7] netxen: onchip memory access change Dhananjay Phadke
2009-10-16 6:09 ` [PATCH NEXT 6/7] netxen: fix error codes in for tools access Dhananjay Phadke
2009-10-16 6:09 ` [PATCH NEXT 7/7] netxen: sysfs control for auto firmware recovery Dhananjay Phadke
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=1255673353-31797-1-git-send-email-dhananjay@netxen.com \
--to=dhananjay@netxen.com \
--cc=davem@davemloft.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox