From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Matthew Garrett <mjg59@google•com>
Cc: James Morris <jmorris@namei•org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
David Howells <dhowells@redhat•com>,
Kees Cook <keescook@chromium•org>
Subject: Re: linux-next: Signed-off-by missing for commit in the security tree
Date: Wed, 21 Aug 2019 10:33:14 +1000 [thread overview]
Message-ID: <20190821103314.426add83@canb.auug.org.au> (raw)
In-Reply-To: <CACdnJuvCQBX7JaajT5upiY-sNrUfS+pmmSqJF-g_mog96A8h1Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
Hi Matthew,
On Tue, 20 Aug 2019 15:39:33 -0700 Matthew Garrett <mjg59@google•com> wrote:
>
> On Tue, Aug 20, 2019 at 3:32 PM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > Hi all,
> >
> > Commit
> >
> > 9d1f8be5cf42 ("bpf: Restrict bpf when kernel lockdown is in confidentiality mode")
> >
> > is missing a Signed-off-by from its author.
>
> I'm providing this under category (c) of the DCO.
That, of course, is fine (but not something that can be deduced from
the commit :-(). Its also a bit confusing since the preceeding patches
are from David and have his SOB ..
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-21 0:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 22:32 linux-next: Signed-off-by missing for commit in the security tree Stephen Rothwell
2019-08-20 22:39 ` Matthew Garrett
2019-08-21 0:33 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-16 6:49 Stephen Rothwell
2024-12-16 22:36 ` Paul Moore
2019-08-11 21:46 Stephen Rothwell
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=20190821103314.426add83@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dhowells@redhat$(echo .)com \
--cc=jmorris@namei$(echo .)org \
--cc=keescook@chromium$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mjg59@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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