From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Lobakin <alobakin@pm.me>,
Sami Tolvanen <samitolvanen@google.com>,
Bill Wendling <morbo@google.com>,
Bjorn Helgaas <bhelgaas@google.com>,
George Burgess IV <gbiv@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Will Deacon <will@kernel.org>
Subject: Re: [GIT PULL v2] clang-lto for v5.12-rc1
Date: Tue, 23 Feb 2021 12:43:36 -0800 [thread overview]
Message-ID: <202102231243.FC8512FE3D@keescook> (raw)
In-Reply-To: <CAHk-=wgQ=oaLD_ybzhOP+8LFNZH3Qzpc-dp4XB4cXxXLReCdnQ@mail.gmail.com>
On Tue, Feb 23, 2021 at 12:33:05PM -0800, Linus Torvalds wrote:
> On Tue, Feb 23, 2021 at 9:49 AM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > On Mon, Feb 22, 2021 at 3:11 PM Kees Cook <keescook@chromium.org> wrote:
> > >
> > > While x86 LTO enablement is done[1], it depends on some objtool
> > > clean-ups[2], though it appears those actually have been in linux-next
> > > (via tip/objtool/core), so it's possible that if that tree lands [..]
> >
> > That tree is actually next on my list of things to merge after this
> > one, so it should be out soonish.
>
> "soonish" turned out to be later than I thought, because my "build
> changes" set of pulls included the module change that I then wasted a
> lot of time on trying to figure out why it slowed down my build so
> much.
>
> But it's out now, as pr-tracker-bot already noted.
Great! Thanks for the updates; I'll prepare "part 2" right away. :)
--
Kees Cook
next prev parent reply other threads:[~2021-02-23 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 23:11 [GIT PULL v2] clang-lto for v5.12-rc1 Kees Cook
2021-02-23 17:49 ` Linus Torvalds
2021-02-23 20:33 ` Linus Torvalds
2021-02-23 20:43 ` Kees Cook [this message]
2021-02-23 20:49 ` Alexander Lobakin
2021-02-24 16:04 ` Arnd Bergmann
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=202102231243.FC8512FE3D@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 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).