From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: James Morris <jmorris@namei.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: bad commits in the security tree
Date: Wed, 23 Nov 2016 04:09:07 +1100 [thread overview]
Message-ID: <20161123040907.708bb4cc@canb.auug.org.au> (raw)
In-Reply-To: <03bf91ac-1f20-1089-79dd-e342c9f610d9@schaufler-ca.com>
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
prev parent reply other threads:[~2016-11-22 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 10:58 linux-next: bad commits in the security tree Stephen Rothwell
2016-11-22 16:17 ` Casey Schaufler
2016-11-22 17:09 ` Stephen Rothwell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161123040907.708bb4cc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).