Request for Patches
The 2.6.x kernel includes a MODULE_VERSION() parameter for providing
one convenient way for all modules to state what *their* version is
(as opposed to the version of the larger kernel they're included in).
I've started submitting patches to the subsystem maintainers to add
MODULE_VERSION() entries for drivers that I particularly care about,
and would appreciate assistance handling the others.
For modules which display their version as a string somewhere via
printk, the preferred mechanism is:
#define DRV_VERSION "1.0.0"
MODULE_VERSION(DRV_VERSION);
One aspect of MODULE_VERSION I haven't tackled is re-formatting
existing versions into the preferred method as found in include/linux/module.h:
/* Version of form [<epoch>:]<version>[-<extra-version>].
Or for CVS/RCS ID version, everything but the number is stripped.
<epoch>: A (small) unsigned integer which allows you to start
versions
anew. If not mentioned, it's zero. eg. "2:1.0" is after
"1:2.0".
<version>: The <version> may contain only alphanumerics and the
character `.'. Ordered by numeric sort for numeric parts,
ascii sort for ascii parts (as per RPM or DEB algorithm).
<extraversion>: Like <version>, but inserted for local
customizations, eg "rh3" or "rusty1".
*/
I leave such reformatting up to each driver author and/or patch
submitter.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
pgpgWqUp9o5cH.pgp
Description: PGP signature
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@xxxxxxxxxxxxxx
http://lists.osdl.org/mailman/listinfo/kernel-janitors
|
