From: Dhananjay Phadke <dhananjay@netxen.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH NEXT v2 7/7] netxen; update version to 4.0.62
Date: Fri, 16 Oct 2009 18:50:12 -0700 [thread overview]
Message-ID: <1255744212-28074-8-git-send-email-dhananjay@netxen.com> (raw)
In-Reply-To: <1255744212-28074-1-git-send-email-dhananjay@netxen.com>
Signed-off-by: Dhananjay Phadke <dhananjay@netxen.com>
---
drivers/net/netxen/netxen_nic.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/netxen/netxen_nic.h b/drivers/net/netxen/netxen_nic.h
index fa7511e..e98cfa6 100644
--- a/drivers/net/netxen/netxen_nic.h
+++ b/drivers/net/netxen/netxen_nic.h
@@ -53,8 +53,8 @@
#define _NETXEN_NIC_LINUX_MAJOR 4
#define _NETXEN_NIC_LINUX_MINOR 0
-#define _NETXEN_NIC_LINUX_SUBVERSION 50
-#define NETXEN_NIC_LINUX_VERSIONID "4.0.50"
+#define _NETXEN_NIC_LINUX_SUBVERSION 62
+#define NETXEN_NIC_LINUX_VERSIONID "4.0.62"
#define NETXEN_VERSION_CODE(a, b, c) (((a) << 24) + ((b) << 16) + (c))
#define _major(v) (((v) >> 24) & 0xff)
--
1.6.0.2
prev parent reply other threads:[~2009-10-17 1:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 1:50 [PATCH NEXT v2 0/7] netxen: changes for future chip revisions Dhananjay Phadke
2009-10-17 1:50 ` [PATCH NEXT v2 1/7] netxen: defines for next revision Dhananjay Phadke
2009-10-17 1:50 ` [PATCH NEXT v2 2/7] netxen: 128 memory controller support Dhananjay Phadke
2009-10-17 1:50 ` [PATCH NEXT v2 3/7] netxen: reset sequence changes Dhananjay Phadke
2009-10-17 1:50 ` [PATCH NEXT v2 4/7] netxen: onchip memory access change Dhananjay Phadke
2009-10-17 1:50 ` [PATCH NEXT v2 5/7] netxen: fix error codes in for tools access Dhananjay Phadke
2009-10-17 1:50 ` [PATCH NEXT v2 6/7] netxen: sysfs control for auto firmware recovery Dhananjay Phadke
2009-10-17 1:50 ` Dhananjay Phadke [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=1255744212-28074-8-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