mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Valerie Henson" <val_henson@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	"Jeff Garzik" <jeff@garzik.org>
Subject: Re: [patch 4/4] [TULIP] Rev tulip version
Date: Mon, 12 Mar 2007 12:44:12 +0200	[thread overview]
Message-ID: <84144f020703120344n3f5ed52axf0bc1c109b549535@mail.gmail.com> (raw)
In-Reply-To: <20070312095912.743760000@linux.intel.com>

Hi,

On 3/12/07, Valerie Henson <val_henson@linux.intel.com> wrote:
> --- tulip-2.6-mm-linux.orig/drivers/net/tulip/tulip_core.c
> +++ tulip-2.6-mm-linux/drivers/net/tulip/tulip_core.c
> @@ -17,11 +17,11 @@
>
>  #define DRV_NAME       "tulip"
>  #ifdef CONFIG_TULIP_NAPI
> -#define DRV_VERSION    "1.1.14-NAPI" /* Keep at least for test */
> +#define DRV_VERSION    "1.1.15-NAPI" /* Keep at least for test */
>  #else
> -#define DRV_VERSION    "1.1.14"
> +#define DRV_VERSION    "1.1.15"
>  #endif
> -#define DRV_RELDATE    "May 11, 2002"
> +#define DRV_RELDATE    "Feb 27, 2007"

Why not just drop this? What purpose does a per-module revision have
for in-kernel drivers anyway?

                                      Pekka

  reply	other threads:[~2007-03-12 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12  9:59 [patch 0/4] [TULIP] Tulip updates Valerie Henson
2007-03-12  9:59 ` [patch 1/4] [TULIP] fix for Lite-On 82c168 PNIC Valerie Henson
2007-03-15 12:40   ` Mikael Pettersson
2007-03-12  9:59 ` [patch 2/4] [TULIP] Quiet down tulip_stop_rxtx Valerie Henson
2007-03-12  9:59 ` [patch 3/4] [TULIP] Fix SytemError typo Valerie Henson
2007-03-12  9:59 ` [patch 4/4] [TULIP] Rev tulip version Valerie Henson
2007-03-12 10:44   ` Pekka Enberg [this message]
2007-03-12 14:07     ` Jeff Garzik
2007-03-13 17:07       ` Andy Gospodarek

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=84144f020703120344n3f5ed52axf0bc1c109b549535@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=val_henson@linux.intel.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

all inboxes | Powered by JetHome®