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]
Message-ID: <4630BD61.2050006@gmail.com>
Date:	Thu, 26 Apr 2007 16:55:29 +0200
From:	Rene Herman <rene.herman@...il.com>
To:	Adrian Bunk <bunk@...sta.de>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	"Robert P. J. Day" <rpjday@...dspring.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Marcel Holtmann <marcel@...tmann.org>,
	Christoph Hellwig <hch@...radead.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: MODULE_MAINTAINER

On 04/26/2007 03:54 PM, Adrian Bunk wrote:

> Let me try to summarize the points:
> - you think MODULE_AUTHOR without MODULE_MAINTAINER confuses users

Yes, and the frustration of composing lengthy emails to bouncing (or worse 
still, silent) email adresses is severe if you just decided to for once not 
shrug about it but submit a bugreport. If it happens to an address from 
MAINTAINERS (and an LKML savvy user) the address can at least be deleted but 
you can't delete a MODULE_AUTHOR tag.

Without something like a MODULE_MAINTAINER I have no way of saying "ignore 
those MODULE_AUTHORs please, I want the bugreport".

> - Alan wants MODULE_AUTHOR to stay for easing showing authorship of code
>   to people
> - I (and others) think MODULE_MAINTAINER wouldn't make sense

Had a few Ays as well. But note, since you suggested removing MODULE_AUTHOR 
I actually agree that made more sense. It's just that iff that can't happen, 
I feel I need a place to override MODULE_AUTHOR for the use that I'm 
interested in and which is acting as the contact for a driver.

> Is there any good solution for this?
> E.g. modinfo could be changed to no longer defaulting to show the author?

Tie Alan to his chair and take away his keyboard while we submit patches 
removing MODULE_AUTHOR? Or just apply a trivial two line, optional, non 
mandatory, patch introducing a MODULE_MAINTAINER? You pick... :-)

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ