From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in Linus' tree
Date: Wed, 24 Feb 2021 11:52:28 -0800 [thread overview]
Message-ID: <202102241146.97ACF2F@keescook> (raw)
In-Reply-To: <20210224113108.4c05915e@canb.auug.org.au>
On Wed, Feb 24, 2021 at 11:31:08AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> b33fff07e3e3 ("x86, build: allow LTO to be selected")
> d2dcd3e37475 ("x86, cpu: disable LTO for cpu.c")
> e242db40be27 ("x86, vdso: disable LTO only for vDSO")
> b1a1a1a09b46 ("kbuild: lto: postpone objtool")
> 41425ebe2024 ("objtool: Split noinstr validation from --vmlinux")
> 6dafca978033 ("x86, build: use objtool mcount")
> 22c8542d7b22 ("tracing: add support for objtool mcount")
> 0e731dbc1824 ("objtool: Don't autodetect vmlinux.o")
> 18a14575ae31 ("objtool: Fix __mcount_loc generation with Clang's assembler")
> 99d0021569c7 ("objtool: Add a pass for generating __mcount_loc")
>
> are missing a Signed-off-by from their committer.
Ieeeee! Ugh, yes, my bad, entirely. I screwed up when rebuilding the
LTO "part 2" series for the -rc1 window (missed the -s on the cherry-pick).
Since we can't change git history, the best fix I can do is send it here
to the list. Obviously, these should all be considered:
Signed-off-by: Kees Cook <keescook@chromium.org>
Again, apologies. I, too, will add a commit hook to check for this. (Is
there an existing script anyone else is already using?)
--
Kees Cook
prev parent reply other threads:[~2021-02-24 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 0:31 linux-next: Signed-off-by missing for commits in Linus' tree Stephen Rothwell
2021-02-24 0:33 ` Linus Torvalds
2021-02-24 0:49 ` Stephen Rothwell
2021-02-24 20:27 ` Kees Cook
2021-02-24 21:30 ` Kees Cook
2021-02-27 23:38 ` Linus Walleij
2021-02-24 19:52 ` Kees Cook [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=202102241146.97ACF2F@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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