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]

Message-ID: <41840b750608060256g1a7bb9c3s843d3ac08e512d63@mail.gmail.com>
Date:	Sun, 6 Aug 2006 12:56:43 +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:
> On Sun, 06 Aug 2006 10:26:46 +0300
> Shem Multinymous <multinymous@...il.com> wrote:
>
> > Signed-off-by: Shem Multinymous <multinymous@...il.com>
>
> This rather defeats the purpose of the DCO.

SubmittingPatches declares the purpose of the DCO as "To improve
tracking of who did what, especially with patches that can percolate
to their final resting place in the kernel through several layers of
maintainers."

I indeed certify  that:

        (a) The contribution was created in whole or in part by me and I
            have the right to submit it under the open source license
            indicated in the file; or

        (b) The contribution is based upon previous work that, to the best
            of my knowledge, is covered under an appropriate open source
            license and I have the right under that license to submit that
            work with modifications, whether created in whole or in part
            by me, under the same open source license (unless I am
            permitted to submit under a different license), as indicated
            in the file; or

        (c) The contribution was provided directly to me by some other
            person who certified (a), (b) or (c) and I have not modified
            it.

        (d) I understand and agree that this project and the contribution
            are public and that a record of the contribution (including all
            personal information I submit with it, including my sign-off) is
            maintained indefinitely and may be redistributed consistent with
            this project or the open source license(s) involved.

Practically speaking, this contact address is stable and reliable.

What more is needed that may be realistically expected from a kernel
patch submission?

  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/