From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc3
Date: Fri, 2 Feb 2024 11:11:08 +0000 [thread overview]
Message-ID: <20240202111107.GA16598@willie-the-truck> (raw)
Hi Linus,
Please pull these two small fixes for -rc3. The first one is an
alternative fix for the SCS patching problem we thought we'd fixed in
-rc1; it turned out not to be robust with all toolchains/configs, so
this is a revert+retry which has seen some more testing.
The other one simply removes an unused header file, but I couldn't
resist the negative diffstat.
There's a crop of fpsimd/SVE/SME fixes pending which I'll probably send
next week once they've been reviewed.
Cheers,
Will
--->8
The following changes since commit 41bccc98fb7931d63d03f326a746ac4d429c1dd3:
Linux 6.8-rc2 (2024-01-28 17:01:12 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
for you to fetch changes up to c7767f5c43df2c453af4651d1f58f489e3eb4ac1:
arm64: vdso32: Remove unused vdso32-offsets.h (2024-01-30 11:59:17 +0000)
----------------------------------------------------------------
arm64 fixes for -rc3
- Really fix shadow call stack patching with LTO=full
- Remove unused (empty) header file generated from the compat vDSO
----------------------------------------------------------------
Ard Biesheuvel (2):
arm64: Revert "scs: Work around full LTO issue with dynamic SCS"
arm64: scs: Disable LTO for SCS patching code
Kevin Brodsky (1):
arm64: vdso32: Remove unused vdso32-offsets.h
arch/arm64/Makefile | 2 +-
arch/arm64/include/asm/vdso.h | 3 ---
arch/arm64/kernel/Makefile | 6 +++---
arch/arm64/kernel/vdso32/Makefile | 9 ---------
4 files changed, 4 insertions(+), 16 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-02-02 11:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 11:11 Will Deacon [this message]
2024-02-02 20:43 ` [GIT PULL] arm64 fixes for -rc3 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-09-22 16:19 Will Deacon
2023-09-22 20:19 ` pr-tracker-bot
2023-05-19 11:46 Will Deacon
2023-05-19 18:32 ` pr-tracker-bot
2022-08-26 17:58 Will Deacon
2022-08-26 19:09 ` pr-tracker-bot
2021-11-26 13:22 Will Deacon
2021-11-26 18:35 ` pr-tracker-bot
2021-07-22 15:55 Will Deacon
2021-07-22 18:00 ` pr-tracker-bot
2021-03-12 13:34 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-12 20:03 ` pr-tracker-bot
2020-11-06 13:20 [GIT PULL] arm64 fixes " Will Deacon
2020-11-06 21:13 ` pr-tracker-bot
2020-06-26 13:21 Will Deacon
2020-06-27 16:00 ` pr-tracker-bot
2020-02-21 16:01 Will Deacon
2020-02-22 0:07 ` Linus Torvalds
2020-02-22 0:15 ` pr-tracker-bot
2019-10-09 13:30 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-09 19:30 ` pr-tracker-bot
2019-05-30 16:11 [GIT PULL] arm64: fixes " Will Deacon
2019-05-31 4:25 ` pr-tracker-bot
2019-01-20 0:04 Will Deacon
2019-01-20 3:29 ` Linus Torvalds
2019-01-20 4:00 ` pr-tracker-bot
2018-04-27 16:23 Will Deacon
2017-12-07 17:58 Will Deacon
2016-10-28 16:01 Will Deacon
2016-02-04 18:49 Will Deacon
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=20240202111107.GA16598@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).