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, 04 Apr 2007 20:01:31 +0200
From:	Rene Herman <rene.herman@...il.com>
To:	Adrian Bunk <bunk@...sta.de>
CC:	Takashi Iwai <tiwai@...e.de>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Marcel Holtmann <marcel@...tmann.org>,
	Christoph Hellwig <hch@...radead.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: MODULE_MAINTAINER

On 04/04/2007 07:48 PM, Adrian Bunk wrote:

> On Wed, Apr 04, 2007 at 07:00:18PM +0200, Takashi Iwai wrote:

>> But in general, it would be nice to have an easy way to find a
>> maintainer (not author) from a module binary, and I agree
>> MODULE_MAINTAINER can work well for such a purpose.  It's no mandatory
>> field, but could be some help.
> 
> Yes, it would be nice.
> 
> But would this information always be kept up-to-date for the whole tree?
> I don't see this happen.

I believe it would largely stay up to date yes. The tag wouldn't be 
mandatory and adding oneself as a MODULE_MAINTAINER would specifically 
be saying "yes, I want to look after this thing". If someone then no 
longer wants to, getting rid of the tag is a matter of deleting one 
line. I wouldn't be worse than MAINTAINERS, and being inline, I expect 
it to be better...

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/