From: "Arnd Bergmann" <arnd@arndb.de>
To: "Safocl Stollmannovic" <safocl88@gmail.com>
Cc: linux-kernel@vger.kernel.org, Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH 09/10] sched/preempt: fix duplicate extern declarations
Date: Fri, 13 Nov 2026 09:37:30 +0100 [thread overview]
Message-ID: <a37c1534-f1d4-4c0c-8aba-955d0742b7b1@app.fastmail.com> (raw)
In-Reply-To: <20261113001432.128201-10-safocl88@gmail.com>
On Fri, Nov 13, 2026, at 01:14, Safocl Stollmannovic wrote:
> 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
The changelog text makes no sense. We don't support building the
kernel with C++ and this is not a user-visible header.
Leaving out the 'extern' in declarations is just a preference
in coding style, no need to send patches for that.
Arnd
next prev parent reply other threads:[~2026-11-13 8:37 UTC|newest]
Thread overview: 15+ 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 ` [PATCH 01/10] ARM: fix " Safocl Stollmannovic
2026-11-13 0:14 ` [PATCH 02/10] loongarch: " 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 8:37 ` Arnd Bergmann [this message]
2026-11-13 0:14 ` [PATCH 10/10] kernel: " Safocl Stollmannovic
2026-11-13 12:02 [PATCH 09/10] sched/preempt: " Safocl
2026-11-13 12:36 ` Arnd Bergmann
2026-11-13 12:48 Safocl
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=a37c1534-f1d4-4c0c-8aba-955d0742b7b1@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=safocl88@gmail.com \
/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®