From: Kees Cook <keescook@chromium.org>
To: Alexander Lobakin <alobakin@pm.me>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Bill Wendling <morbo@google.com>,
Bjorn Helgaas <bhelgaas@google.com>,
George Burgess IV <gbiv@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Will Deacon <will@kernel.org>
Subject: Re: [GIT PULL] clang-lto for v5.12-rc1
Date: Wed, 17 Feb 2021 10:08:28 -0800 [thread overview]
Message-ID: <202102171006.DD2F341@keescook> (raw)
In-Reply-To: <20210216224751.7367-1-alobakin@pm.me>
On Tue, Feb 16, 2021 at 10:48:10PM +0000, Alexander Lobakin wrote:
> From: Kees Cook <keescook@chromium.org>
> Date: Tue, 16 Feb 2021 12:34:37 -0800
>
> > Hi Linus,
> >
> > Please pull this Clang Link Time Optimization series for v5.12-rc1. This
> > has been in linux-next for the entire last development cycle, and is
> > built on the work done preparing[0] for LTO by arm64 folks, tracing folks,
> > etc. This series includes the core changes as well as the remaining pieces
> > for arm64 (LTO has been the default build method on Android for about
> > 3 years now, as it is the prerequisite for the Control Flow Integrity
> > protections). While x86 LTO support is done[1], there is still some
> > on-going clean-up work happening for objtool[2] that should hopefully
> > land by the v5.13 merge window.
>
[...]
>
> Seems like you forgot the fix from [0], didn't you?
>
[...]
>
> [0] https://lore.kernel.org/lkml/20210121184544.659998-1-alobakin@pm.me
Ah yes, sorry for overlooking that. I can send a follow-up PR. AIUI,
it's usually better for Linus's workflow for me to build on sent PRs
instead of resending. (But given the merge window disruption, we'll see
what happens!)
--
Kees Cook
next prev parent reply other threads:[~2021-02-17 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 22:48 [GIT PULL] clang-lto for v5.12-rc1 Alexander Lobakin
2021-02-17 18:08 ` Kees Cook [this message]
2021-02-22 21:59 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2021-02-16 20:34 Kees Cook
2021-02-23 20:32 ` pr-tracker-bot
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=202102171006.DD2F341@keescook \
--to=keescook@chromium.org \
--cc=alobakin@pm.me \
--cc=bhelgaas@google.com \
--cc=gbiv@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morbo@google.com \
--cc=ndesaulniers@google.com \
--cc=rostedt@goodmis.org \
--cc=samitolvanen@google.com \
--cc=torvalds@linux-foundation.org \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.