Hi Rusty.
Following up the recent MODULE_MAINTAINER discussion:
http://lkml.org/lkml/2007/4/4/170
that concluded with MODULE_MAINTAINER not being a good idea, here's a small
patch that just deletes the advice of including an email address in the
MODULE_AUTHOR tag as suggested (and not objected to) at the end of it.
The email address is the problem I was trying to fix; with multiple current
and non-current authors and maintainers who might not even be authors the
address(es) available from the tag confuse the issue of whom to contact.
It's moreover also information that easily outdated.
A bit more than half of the tags in the tree don't include an email address
already and I'll submit patches removing more...
Rene.
commit 3b4fa382d5a6a3d9afdcb5a9232d63c47391fb30
Author: Rene Herman <[email protected]>
Date: Fri May 11 02:24:35 2007 +0200
module_author: don't advice putting in an email address
It's information that's easily outdated and easily mistaken for
a driver contact which is a problem especially for modules with
multiple current and non-current authors as well as for modules
with a maintainer who may not even be a module author.
Signed-off-by: Rene Herman <[email protected]>
diff --git a/include/linux/module.h b/include/linux/module.h
index 792d483..e6e0f86 100644
--- a/include/linux/module.h
+++ b/include/linux/module.h
@@ -124,7 +124,7 @@ extern struct module __this_module;
*/
#define MODULE_LICENSE(_license) MODULE_INFO(license, _license)
-/* Author, ideally of form NAME <EMAIL>[, NAME <EMAIL>]*[ and NAME <EMAIL>] */
+/* Author, ideally of form NAME[, NAME]*[ and NAME] */
#define MODULE_AUTHOR(_author) MODULE_INFO(author, _author)
/* What your module does. */
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
