From: Safocl Stollmannovic <safocl88@gmail.com>
To: Russell King <linux@armlinux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 01/10] ARM: fix duplicate extern declarations
Date: Fri, 13 Nov 2026 04:14:07 +0400 [thread overview]
Message-ID: <20261113001432.128201-2-safocl88@gmail.com> (raw)
In-Reply-To: <20261113001432.128201-1-safocl88@gmail.com>
Compiling a kernel module with a C++ compiler results in a duplicate
echo ‘extern’ specifier error.
This occurs because the code contains , and
expands to when processed by a C++ compiler.
The specifier must be removed.
https://bugzilla.kernel.org/show_bug.cgi?id=222257
Signed-off-by: Safocl Stollmannovic <safocl88@gmail.com>
---
arch/arm/include/asm/bug.h | 2 +-
arch/arm/include/asm/opcodes.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/include/asm/bug.h b/arch/arm/include/asm/bug.h
index ba8d9d7d2..985857d65 100644
--- a/arch/arm/include/asm/bug.h
+++ b/arch/arm/include/asm/bug.h
@@ -82,7 +82,7 @@ void hook_ifault_code(int nr, int (*fn)(unsigned long, unsigned int,
struct pt_regs *),
int sig, int code, const char *name);
-extern asmlinkage void c_backtrace(unsigned long fp, int pmode,
+asmlinkage void c_backtrace(unsigned long fp, int pmode,
const char *loglvl);
struct mm_struct;
diff --git a/arch/arm/include/asm/opcodes.h b/arch/arm/include/asm/opcodes.h
index 38e3eabff..afa29833f 100644
--- a/arch/arm/include/asm/opcodes.h
+++ b/arch/arm/include/asm/opcodes.h
@@ -8,7 +8,7 @@
#ifndef __ASSEMBLY__
#include <linux/linkage.h>
-extern asmlinkage unsigned int arm_check_condition(u32 opcode, u32 psr);
+asmlinkage unsigned int arm_check_condition(u32 opcode, u32 psr);
#endif
#define ARM_OPCODE_CONDTEST_FAIL 0
--
2.56.1
next prev parent reply other threads:[~2026-11-13 0:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 0:14 [PATCH 00/10] Remove " Safocl Stollmannovic
2026-11-13 0:14 ` Safocl Stollmannovic [this message]
2026-11-13 0:14 ` [PATCH 02/10] loongarch: fix " Safocl Stollmannovic
2026-11-13 0:14 ` [PATCH 03/10] microblaze: " Safocl Stollmannovic
2026-11-13 0:14 ` [PATCH 04/10] MIPS: " Safocl Stollmannovic
2026-11-13 0:14 ` [PATCH 05/10] openrisc: " Safocl Stollmannovic
2026-11-13 0:14 ` [PATCH 06/10] riscv: " Safocl Stollmannovic
2026-11-13 0:14 ` [PATCH 07/10] x86: " Safocl Stollmannovic
2026-11-13 0:14 ` [PATCH 08/10] drivers: " Safocl Stollmannovic
2026-11-13 0:14 ` [PATCH 09/10] sched/preempt: " Safocl Stollmannovic
2026-11-13 0:14 ` [PATCH 10/10] kernel: " Safocl Stollmannovic
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=20261113001432.128201-2-safocl88@gmail.com \
--to=safocl88@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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
all inboxes | Powered by JetHome®