| 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
| ||
|
Date: Wed, 04 Apr 2007 15:02:41 +0200 From: Rene Herman <rene.herman@...il.com> To: Christoph Hellwig <hch@...radead.org> CC: Rusty Russell <rusty@...tcorp.com.au>, Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: MODULE_MAINTAINER On 04/04/2007 02:33 PM, Christoph Hellwig wrote: > On Wed, Apr 04, 2007 at 01:26:04PM +0200, Rene Herman wrote: >> Can we have a MODULE_MAINTAINER to complement MODULE_AUTHOR? > > #define MODULE_MAINTAINER(x) MODULE_AUTHOR(x), please. > MODULE_AUTHOR really has meant maintainer in practice for ages, and it's > the only actually relevant for users information we should store. Given modules with multiple authors, current and non-current, I believe having "modinfo -m" tell the user whom to contact is an avantage. Rene. - 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/
Powered by blists - more mailing lists