Thread (8 messages) 8 messages, 5 authors, 2008-08-23

RE: [PATCH 4/4 2.6.28] cxgb3i - cxgb3i iscsi driver

From: <hidden>
Date: 2008-08-23 09:09:14
Also in: linux-scsi, lkml

David Miller wrote: 
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help