From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Alexander Lobakin <alobakin@pm.me>,
Linux Kernel Mailing List <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: Mon, 22 Feb 2021 13:59:06 -0800 [thread overview]
Message-ID: <CAHk-=wjvSLSKsa5ZbBCTqszv3XXdvQNRTQk8adFApA7MbK5+ng@mail.gmail.com> (raw)
In-Reply-To: <202102171006.DD2F341@keescook>
On Wed, Feb 17, 2021 at 10:08 AM Kees Cook <keescook@chromium.org> wrote:
>
> 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!)
Since I'm only now getting around to looking at the stuff that wasn't
obvious, can you just add the fix and send a new pull request for the
fixed version?
Power seems fine, I got internet back on today too (I was working by
tethering off my phone over the weekend), so I should be all back to
normal.
Linus
next prev parent reply other threads:[~2021-02-22 22:00 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
2021-02-22 21:59 ` Linus Torvalds [this message]
-- 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='CAHk-=wjvSLSKsa5ZbBCTqszv3XXdvQNRTQk8adFApA7MbK5+ng@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=alobakin@pm.me \
--cc=bhelgaas@google.com \
--cc=gbiv@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morbo@google.com \
--cc=ndesaulniers@google.com \
--cc=rostedt@goodmis.org \
--cc=samitolvanen@google.com \
--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).