From: Brice Goglin <brice@myri.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: netdev@vger.kernel.org
Subject: [PATCH 3/3] myri10ge: update driver version
Date: Wed, 30 May 2007 21:15:14 +0200 [thread overview]
Message-ID: <465DCD42.7070608@myri.com> (raw)
In-Reply-To: <465DCCB4.5040404@myri.com>
Update driver version to 1.3.1-1.245.
Signed-off-by: Brice Goglin <brice@myri.com>
---
drivers/net/myri10ge/myri10ge.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-rc/drivers/net/myri10ge/myri10ge.c
===================================================================
--- linux-rc.orig/drivers/net/myri10ge/myri10ge.c 2007-05-30 20:58:34.000000000 +0200
+++ linux-rc/drivers/net/myri10ge/myri10ge.c 2007-05-30 20:58:41.000000000 +0200
@@ -71,7 +71,7 @@
#include "myri10ge_mcp.h"
#include "myri10ge_mcp_gen_header.h"
-#define MYRI10GE_VERSION_STR "1.3.0-1.233"
+#define MYRI10GE_VERSION_STR "1.3.1-1.245"
MODULE_DESCRIPTION("Myricom 10G driver (10GbE)");
MODULE_AUTHOR("Maintainer: help@myri.com");
next prev parent reply other threads:[~2007-05-30 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 19:12 [PATCH 0/3] myri10ge updates for 2.6.22 Brice Goglin
2007-05-30 19:13 ` [PATCH 1/3] myri10ge: report link up/down in standard ethtool way Brice Goglin
2007-06-03 15:48 ` Jeff Garzik
2007-05-30 19:14 ` [PATCH 2/3] myri10ge: limit the number of recoveries Brice Goglin
2007-06-03 15:55 ` Jeff Garzik
2007-06-04 17:07 ` [PATCH 0/1] " Brice Goglin
2007-06-04 17:08 ` [PATCH 1/1] " Brice Goglin
2007-05-30 19:15 ` Brice Goglin [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-11 18:25 [PATCH 0/3] myri10ge updates Brice Goglin
2007-06-11 18:27 ` [PATCH 3/3] myri10ge: update driver version Brice Goglin
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=465DCD42.7070608@myri.com \
--to=brice@myri.com \
--cc=jeff@garzik.org \
--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;
as well as URLs for NNTP newsgroup(s).