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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date:	Sat, 31 Dec 2011 23:16:54 -0800
From:	Roland Dreier <>
To:	Steve Hodgson <>
Cc:	Andrew Morton <>,
	Jörn Engel <>,
Subject: Re: [PATCH] btree: Export btree_get_prev() so modules can use btree_for_each

On Sat, Dec 31, 2011 at 7:22 PM, Steve Hodgson <> wrote:
> Signed-off-by: Steve Hodgson
> Or you would prefer the patch is resent with my Sign-off in the commit
> message?

A properly formed S-o-b line has the email address too... but in any case I
don't think it should be necessary in this case.  First of all the patch is a
pretty trivial one-liner... but in any case as I understand things I should be
able to submit patches from our company's internal tree and both preserve
authorship (ie "From: Steve") but also be the first person sending it out.

Looking at "Developer's Certificate of Origin 1.1" in SubmittingPatches, I
guess I am certifying (b), ie

        (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

(Since I actually did write the changelog for the patch)

 - R.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists