lkml.org 
[lkml]   [2004]   [Oct]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [patch 2.6.9 0/11] Add MODULE_VERSION to several network drivers
From
Date
On Thu, 2004-10-21 at 14:22, John W. Linville wrote:
>
> > have you checked if the version of these drivers is actually useful? (eg
> > updated when the driver changes) If it's not I'd say adding a
> > MODULE_VERSION to it makes no sense whatsoever.
>
> Why do I feel like I'm being baited...? :-)
>
> I would have to suspect that if a version string exists, that it has at
> least some meaning to the primary developers/maintainters. It certainly
> is beyond my control to force the maintainers to give meaning to their
> version strings.

Since the skeleton driver includes a define for that, I suspect your
assumption is a bit overly optimistic.

> Is this a political statement against the MODULE_VERSION macro and/or
> its purpose? I'm not overly interested in debating that one...

Not really. I have absolutely no problem with a MODULE_VERSION macro
*IF* the version it advertises means something. However if the version
it advertises has no meaning whatsoever (eg the version number never
gets updated) then imo it's better to NOT advertise anything so that
other tools (like dkms) don't make assumptions and decisions based on
nothing-meaning data.

-
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/

\
 
 \ /
  Last update: 2005-03-22 14:07    [W:0.052 / U:1.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site