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 19:00:18 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Rene Herman <rene.herman@...il.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, Adrian Bunk <bunk@...sta.de>,
	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

At Wed, 04 Apr 2007 18:38:42 +0200,
Rene Herman wrote:
> 
> Other cases-in-point; I've lately been rummaging through sound/isa a 
> bit. Nothing much copyrightable again but especially in those situations 
> where (some of the) original authors are no longer active, I do again 
> want people to contact me about them if needed. And all the "which one 
> of the three people listed here is maintaining this" is yet another.

Practically, the information can go through subsystem maintainers to
specific person (you) in such a case, as the tree is still more or
less maintained by subsystem maintainers.

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.


Takashi
-
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/