From: Ard Biesheuvel <ardb+git@google.com>
To: linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, will@kernel.org, mark.rutland@arm.com,
Ard Biesheuvel <ardb@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Kees Cook <kees@kernel.org>,
Nathan Chancellor <nathan@kernel.org>
Subject: [PATCH 3/3] arm64/scs: Drop unused prototype __pi_scs_patch_vmlinux()
Date: Wed, 6 Nov 2024 19:55:17 +0100 [thread overview]
Message-ID: <20241106185513.3096442-8-ardb+git@google.com> (raw)
In-Reply-To: <20241106185513.3096442-5-ardb+git@google.com>
From: Ard Biesheuvel <ardb@kernel.org>
The function scs_patch_vmlinux() was removed in the LPA2 boot code
refactoring so remove the declaration as well.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
---
arch/arm64/include/asm/scs.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/include/asm/scs.h b/arch/arm64/include/asm/scs.h
index 934e9217cd74..a76f9b387a26 100644
--- a/arch/arm64/include/asm/scs.h
+++ b/arch/arm64/include/asm/scs.h
@@ -54,7 +54,6 @@ enum {
};
int __pi_scs_patch(const u8 eh_frame[], int size);
-asmlinkage void __pi_scs_patch_vmlinux(void);
#endif /* __ASSEMBLY __ */
--
2.47.0.277.g8800431eea-goog
next prev parent reply other threads:[~2024-11-06 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 18:55 [PATCH 0/3] arm64: Dynamic shadow call stack fixes Ard Biesheuvel
2024-11-06 18:55 ` [PATCH 1/3] arm64/scs: Fix handling of DWARF augmentation data in CIE/FDE frames Ard Biesheuvel
2024-11-06 22:13 ` Sami Tolvanen
2024-11-08 14:14 ` Ard Biesheuvel
2024-11-06 18:55 ` [PATCH 2/3] arm64/scs: Deal with 64-bit relative offsets in FDE frames Ard Biesheuvel
2024-11-06 18:55 ` Ard Biesheuvel [this message]
2024-11-06 22:13 ` [PATCH 0/3] arm64: Dynamic shadow call stack fixes Sami Tolvanen
2024-11-08 16:50 ` Catalin Marinas
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=20241106185513.3096442-8-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nathan@kernel.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).