Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753289AbYHWJJO (ORCPT ); Sat, 23 Aug 2008 05:09:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752088AbYHWJI5 (ORCPT ); Sat, 23 Aug 2008 05:08:57 -0400 Received: from ausc60ps301.us.dell.com ([143.166.148.206]:63224 "EHLO ausc60ps301.us.dell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752085AbYHWJI4 convert rfc822-to-8bit (ORCPT ); Sat, 23 Aug 2008 05:08:56 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT Subject: RE: [PATCH 4/4 2.6.28] cxgb3i - cxgb3i iscsi driver Date: Sat, 23 Aug 2008 14:37:53 +0530 Message-ID: <46A00B48CC54E4468EF6911F877AC4CA018D73BC@blrx3m10.blr.amer.dell.com> In-Reply-To: <20080823.012830.262443664.davem@davemloft.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PATCH 4/4 2.6.28] cxgb3i - cxgb3i iscsi driver thread-index: AckE+jvcAUzEcXJFQCqRPbtIa+rXlAABLLqw References: <200808221840.m7MIeuvB004442@localhost.localdomain><20080822124844.b05ee3e8.akpm@linux-foundation.org><46A00B48CC54E4468EF6911F877AC4CA018D73BB@blrx3m10.blr.amer.dell.com> <20080823.012830.262443664.davem@davemloft.net> From: To: Cc: , , , , , , , , , , , , , , , X-OriginalArrivalTime: 23 Aug 2008 09:07:53.0480 (UTC) FILETIME=[B9A8F880:01C904FF] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1212 Lines: 29 > David Miller wrote: > > Andrew Morton wrote: > >I'd suggest that the version number just be removed. It becomes > meaningless (and often misleading) once a driver is in the mainline > kernel. People will >update the driver without changing the version > number. Code external to the driver but which affects it can change. >I totally disagree. I find it very useful when I get a debugging dump from the user and they have no idea where their kernel came from nor can figure >out how to determine the kernel version. >Sure it might sometimes not get updated for trivial patches that bypass the maintainer, but the maintainer is always going to bump it after non-trivial >changes. Exactly. And I am also suggesting that the driver version is not standard among different vendors. So, why not get them generated in an automatic build process. Something like "kernel-version.driver-version". I am just imagining here. The details can be worked out. -Shyam -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/