linux-kernel - Re: MODULE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Apr 2007 18:18:56 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Rene Herman <rene.herman@...il.com>
Cc:	"Robert P. J. Day" <rpjday@...dspring.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Adrian Bunk <bunk@...sta.de>,
	Marcel Holtmann <marcel@...tmann.org>,
	Christoph Hellwig <hch@...radead.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: MODULE_MAINTAINER

On Mon, 23 Apr 2007 14:32:36 +0200 Rene Herman <rene.herman@...il.com> wrote:

> Provide MODULE_MAINTAINER() as a convenient place to stick a name and email 
> address both for drivers having multiple (current and non-current) authors 
> and for when someone who wants to maintain a driver isn't so much an author.
> 
> Signed-off-by: Rene Herman <rene.herman@...il.com>
> ===
> 
> Rene.
> 
> 
> 
> [module_maintainer2.diff  text/plain (604B)]
> diff --git a/include/linux/module.h b/include/linux/module.h
> index 10f771a..3c54774 100644
> --- a/include/linux/module.h
> +++ b/include/linux/module.h
> @@ -128,6 +128,10 @@ extern struct module __this_module;
>  /* Author, ideally of form NAME <EMAIL>[, NAME <EMAIL>]*[ and NAME <EMAIL>] */
>  #define MODULE_AUTHOR(_author) MODULE_INFO(author, _author)
>    
> +/* Maintainer, ideally of form NAME <EMAIL> */
> +#define MODULE_MAINTAINER(_maintainer) \
> +	MODULE_AUTHOR("(Maintained by) "_maintainer)
> +

I'm not sure we want to do this - that's what ./MAINTAINERS is for and we
end up having to maintain the same info in two places.

I actually use git-whatchanged if I'm unsure who to blame^Wask for help on
a particular piece of code.

An easy way of doing this is to go to
http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree
then drill down to the file and hit the "history" link.  That will tell you who
is *really* doing work on the particular code.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/