linux-kernel - Re: linux-next: bad commits in the security tree

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] [day] [month] [year] [list]

Date:   Wed, 23 Nov 2016 04:09:07 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Casey Schaufler <casey@...aufler-ca.com>
Cc:     James Morris <jmorris@...ei.org>, linux-next@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: linux-next: bad commits in the security tree

Hi Casey,

On Tue, 22 Nov 2016 08:17:24 -0800 Casey Schaufler <casey@...aufler-ca.com> wrote:
>
> On 11/22/2016 2:58 AM, Stephen Rothwell wrote:
> > Hi James,
> >
> > I noticed that there are some commits in the security tree that have no
> > Signed-off-by from the committer (Casey Schaufler).
> >  
> My understanding is that patches I don't write should
> be Acked, not Signed-off when I commit them. If this is
> not correct I will address my misconduct.

If you are on the path of a patch to Linus, you need to sign off on the
patch according to the DCO - see section 11 of
Documentation/SubmittingPatches (or
Documentation/process/submitting-patches.rst where it has been moved
recently).

-- 
Cheers,
Stephen Rothwell