All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Safocl Stollmannovic" <safocl88@gmail.com>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
	"Thomas Gleixner" <tglx@kernel.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Pavel Machek" <pavel@kernel.org>,
	"Richard Weinberger" <richard@nod.at>,
	"Anton Ivanov" <anton.ivanov@cambridgegreys.com>,
	"Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-efi@vger.kernel.org
Subject: Re: [PATCH 07/10] x86: fix duplicate extern declarations
Date: Fri, 13 Nov 2026 00:22:55 +0000	[thread overview]
Message-ID: <sashiko-outbox-211988@kernel.org> (raw)
In-Reply-To: <20261113001432.128201-8-safocl88@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] x86: commit message corrupted by shell expansion and inaccurate
  for .c files
--

commit ef771365acc78fbcdae41e8e72ef9a5cfb5a3f35
Author: Safocl Stollmannovic <safocl88@gmail.com>

> x86: fix duplicate extern declarations
>
> 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>

[Severity: Low]
Was the commit message corrupted by unescaped shell command substitution?
The terms "extern asmlinkage", "asmlinkage", "extern \"C\"", and "extern"
are missing from the sentences, and a stray "echo" appears on the second
line.

Also, is the C++ module rationale accurate here?  The kernel does not
support compiling modules or internal headers with a C++ compiler, and
arch/x86/um/sys_call_table_32.c and arch/x86/um/sys_call_table_64.c are C
translation units rather than headers included by modules.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261113001432.128201-1-safocl88@gmail.com?part=7

  reply	other threads:[~2026-11-13  0:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13  0:14 [PATCH 00/10] Remove duplicate extern declarations 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   ` Safocl Stollmannovic
2026-11-13  0:14 ` [PATCH 07/10] x86: " Safocl Stollmannovic
2026-11-13  0:22   ` sashiko-bot [this message]
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=sashiko-outbox-211988@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-efi@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pavel@kernel.org \
    --cc=rafael@kernel.org \
    --cc=richard@nod.at \
    --cc=safocl88@gmail.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tglx@kernel.org \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.