netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@oss.sgi.com, jgarzik@pobox.com,
	ayyappan.veeraiyan@intel.com, john.ronciak@intel.com,
	ganesh.venkatesan@intel.com
Subject: [patch netdev-2.6] e1000: add MODULE_VERSION
Date: Wed, 30 Mar 2005 13:44:03 -0500	[thread overview]
Message-ID: <20050330184403.GD10049@tuxdriver.com> (raw)

Add MODULE_VERSION entry.

Signed-off-by: John W. Linville <linville@tuxdriver.com>
---
I posted one like this before, but it seems to have been lost or
overwritten...

 drivers/net/e1000/e1000_main.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletion(-)

--- netdev-2.6/drivers/net/e1000/e1000_main.c.orig	2005-03-30 13:30:02.355409590 -0500
+++ netdev-2.6/drivers/net/e1000/e1000_main.c	2005-03-30 13:31:13.174846755 -0500
@@ -65,7 +65,8 @@ char e1000_driver_string[] = "Intel(R) P
 #else
 #define DRIVERNAPI "-NAPI"
 #endif
-char e1000_driver_version[] = "5.7.6-k2"DRIVERNAPI;
+#define DRV_VERSION "5.7.6-k2"DRIVERNAPI
+char e1000_driver_version[] = DRV_VERSION;
 char e1000_copyright[] = "Copyright (c) 1999-2004 Intel Corporation.";
 
 /* e1000_pci_tbl - PCI Device ID Table
@@ -210,6 +211,7 @@ static struct pci_driver e1000_driver = 
 MODULE_AUTHOR("Intel Corporation, <linux.nics@intel.com>");
 MODULE_DESCRIPTION("Intel(R) PRO/1000 Network Driver");
 MODULE_LICENSE("GPL");
+MODULE_VERSION(DRV_VERSION);
 
 static int debug = NETIF_MSG_DRV | NETIF_MSG_PROBE;
 module_param(debug, int, 0);
-- 
John W. Linville
linville@tuxdriver.com

             reply	other threads:[~2005-03-30 18:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 18:44 John W. Linville [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-31 16:42 [patch netdev-2.6] e1000: add MODULE_VERSION Venkatesan, Ganesh

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=20050330184403.GD10049@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ayyappan.veeraiyan@intel.com \
    --cc=ganesh.venkatesan@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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).