linux-kernel - Re: [PATCH 01/12] thinkpad_ec: New driver for ThinkPad embedded controller access

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:	Sun, 6 Aug 2006 13:44:02 +0300
From:	"Shem Multinymous" <multinymous@...il.com>
To:	"Andrew Morton" <akpm@...l.org>
Cc:	rlove@...ve.org, khali@...ux-fr.org, gregkh@...e.de,
	alan@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org,
	hdaps-devel@...ts.sourceforge.net
Subject: Re: [PATCH 01/12] thinkpad_ec: New driver for ThinkPad embedded controller access

Hi,

On 8/6/06, Andrew Morton <akpm@...l.org> wrote:
> I suggested a simple solution: Perhaps one of the other project members
> (ie: one who uses a real name) could also sign off the patches?

Well, I offer this patch under the GPL, so anyone (including you) can do it.

But I would like to be able to submit further patches without "adult
supervision", so I hope you don't mind my pressing the issue:


> > What more is needed that may be realistically expected from a kernel
> > patch submission?
>
> We who accept the submission would be making a joke of the whole thing if
> we accepted the assurances of a person who is concealing his/her identity.

Can you please be more specific? What purpose does this exclusion
serve, that would be realistically achieved otherwise? You already
have a GPL license from the author, and a way to contact and uniquely
identify the author.

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