[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45F55EA5.9080005@garzik.org>
Date: Mon, 12 Mar 2007 10:07:33 -0400
From: Jeff Garzik <jeff@...zik.org>
To: Pekka Enberg <penberg@...helsinki.fi>
CC: Valerie Henson <val_henson@...ux.intel.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [patch 4/4] [TULIP] Rev tulip version
Pekka Enberg wrote:
> Hi,
>
> On 3/12/07, Valerie Henson <val_henson@...ux.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?
It's the maintainer's call. Sometimes it eases parsing bug reports, and
tracking changes as your drivers get backported to various enterprise
operating systems(tm). Sometimes it just gets in the way.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists