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

From	Stephen Rothwell <sfr@canb.auug.org.au>
Newsgroups	linux.kernel
Subject	Re: linux-next: bad commits in the security tree
Date	2016-11-22 18:10 +0100
Message-ID	<sGmJX-1DN-33@gated-at.bofh.it> (permalink)
References	<sGgXT-65c-15@gated-at.bofh.it> <sGlXA-18B-27@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Hi Casey,

On Tue, 22 Nov 2016 08:17:24 -0800 Casey Schaufler <casey@schaufler-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

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

linux-next: bad commits in the security tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-11-22 12:00 +0100
  Re: linux-next: bad commits in the security tree Casey Schaufler <casey@schaufler-ca.com> - 2016-11-22 17:20 +0100
    Re: linux-next: bad commits in the security tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-11-22 18:10 +0100

csiph-web