linux-kernel - Re: [PATCH] module: preferred way to use 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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 3 Sep 2009 13:12:03 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Luciano Coelho <luciano.coelho@...ia.com>
Subject: Re: [PATCH] module: preferred way to use MODULE_AUTHOR

On Fri, 28 Aug 2009, Johannes Berg wrote:

> For the longest time now we've been using multiple
> MODULE_AUTHOR() statements when a module has more
> than one author, but the comment here disagrees.
> 
> Signed-off-by: Johannes Berg <johannes@...solutions.net>
> ---
>  include/linux/module.h |    5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> --- wireless-testing.orig/include/linux/module.h	2009-08-28 11:12:34.000000000 +0200
> +++ wireless-testing/include/linux/module.h	2009-08-28 11:13:52.000000000 +0200
> @@ -127,7 +127,10 @@ extern struct module __this_module;
>   */
>  #define MODULE_LICENSE(_license) MODULE_INFO(license, _license)
>  
> -/* Author, ideally of form NAME[, NAME]*[ and NAME] */
> +/*
> + * Author(s), use "Name <email>" or just "Name", for multiple
> + * authors use multiple MODULE_AUTHOR() statements/lines.
> + */
>  #define MODULE_AUTHOR(_author) MODULE_INFO(author, _author)
>    
>  /* What your module does. */

Applied, thanks Johannes.

-- 
Jiri Kosina
SUSE Labs
--
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/