From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Kees Cook <keescook@chromium.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>
Subject: [GIT PULL] clang-lto fixes for v5.12-rc1
Date: Thu, 25 Feb 2021 12:53:52 -0800 [thread overview]
Message-ID: <202102251252.C5A522755@keescook> (raw)
Hi Linus,
Please pull these clang-lto fixes for v5.12-rc1. This gets parisc
building again and moves LTO artifact caching cleanup from the
"distclean" build target to "clean".
Thanks!
-Kees
The following changes since commit 5e95325fbbbdea96de91e7bdb05fe95a3031e37d:
kbuild: lto: force rebuilds when switching CONFIG_LTO (2021-02-23 14:10:44 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/clang-lto-v5.12-rc1-fix1
for you to fetch changes up to 4c7858b9001c85aacf86a74b3a68aa384bc33760:
kbuild: Move .thinlto-cache removal to 'make clean' (2021-02-25 12:21:06 -0800)
----------------------------------------------------------------
clang-lto fixes for v5.12-rc1
- Fix parisc build for ftrace vs mcount (Sami Tolvanen)
- Move .thinlto-cache remove to "clean" from "distclean" (Masahiro Yamada)
----------------------------------------------------------------
Masahiro Yamada (1):
kbuild: Move .thinlto-cache removal to 'make clean'
Sami Tolvanen (1):
parisc: select FTRACE_MCOUNT_USE_PATCHABLE_FUNCTION_ENTRY
Makefile | 4 ++--
arch/parisc/Kconfig | 1 +
2 files changed, 3 insertions(+), 2 deletions(-)
--
Kees Cook
next reply other threads:[~2021-02-25 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 20:53 Kees Cook [this message]
2021-02-26 18:32 ` [GIT PULL] clang-lto fixes for v5.12-rc1 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=202102251252.C5A522755@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=masahiroy@kernel.org \
--cc=samitolvanen@google.com \
--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;
as well as URLs for NNTP newsgroup(s).