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 18:33:06 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Adrian Bunk <bunk@...sta.de>
CC:	Rene Herman <rene.herman@...il.com>,
	Christoph Hellwig <hch@...radead.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: MODULE_MAINTAINER

Adrian Bunk wrote:
> On Wed, Apr 04, 2007 at 03:02:41PM +0200, Rene Herman wrote:
>> Given modules with multiple authors, current and non-current, I believe 
>> having "modinfo -m" tell the user whom to contact is an avantage.
> 
> Much bigger problems are:
> - Who will maintain this information properly?
> - What about modules that are maintained implicitely by the subsystem
>   maintainer?
> 
> And often a user can't be expected to locate the source of a problem, or 
> it might not be in a driver but in a subsystem.
> 
> For vendor kernels, the user should contact the vendor.
> For ftp.kernel.org kernels, I don't see any better solution than telling 
> people to report problems to linux-kernel or the kernel Bugzilla and 
> routing them further from here.

Generelly it has to be kept in mind that there are different contacts
for different purposes:
  - usage problems --> get in touch with the _support_
  - bug reports --> get in touch with _maintainers_
  - development --> get in touch with maintainers/ kernel hackers/
    copyright holders...

The Amiga keyboard had a [Help] key, but this is not how it works.
-- 
Stefan Richter
-=====-=-=== -=-- --=--
http://arcgraph.de/sr/
-
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/