All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Nicolas Schier <nsc@kernel.org>,
	Hamdy Abou El Anein <info@daylightlinux.ch>,
	hamdy.aea@protonmail.com, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: detect module name collisions between '-' and '_'
Date: Mon, 9 Nov 2026 01:49:30 -0500	[thread overview]
Message-ID: <20261109064930.GA829325@ax162> (raw)
In-Reply-To: <20261108225808.1809266-1-sashal@kernel.org>

On Sun, Nov 08, 2026 at 05:58:08PM -0500, Sasha Levin wrote:
> On Sat, 07 Nov 2026 14:14:49 +0100, Nicolas Schier wrote:
> >Applied to kbuild/linux.git (kbuild-next-unstable), with 'Fixes:' tag added, thanks!
> >
> >[1/1] kbuild: detect module name collisions between '-' and '_'
> >      https://git.kernel.org/kbuild/c/bc348949
> 
> With this applied, ARCH=arm allmodconfig fails in modules_check on two
> pairs of modules that have been in the tree for years:

Thanks a lot for the report. I tested arm64 and x86_64 allmodconfig but
failed to do arm. I sent the following patches for these.

>   error: the following would cause module name conflict:
>     drivers/input/apm-power.ko
>     drivers/power/supply/apm_power.ko

https://lore.kernel.org/20261109-apm-power-input-rename-v1-1-0609e7b91825@kernel.org/

>   error: the following would cause module name conflict:
>     arch/arm/probes/kprobes/test-kprobes.ko
>     lib/tests/test_kprobes.ko

https://lore.kernel.org/20261109-arm-test-kprobes-rename-v1-1-663cdbbb90c7@kernel.org/

-- 
Cheers,
Nathan

      reply	other threads:[~2026-11-09  6:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 11:04 [PATCH] kbuild: detect module name collisions between '-' and '_' Hamdy Abou El Anein
2026-11-06  3:31 ` Nathan Chancellor
2026-11-06  7:30   ` Hamdy Abou El Anein
2026-11-07 13:14 ` Nicolas Schier
2026-11-08 22:58   ` Sasha Levin
2026-11-09  6:49     ` Nathan Chancellor [this message]

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=20261109064930.GA829325@ax162 \
    --to=nathan@kernel.org \
    --cc=hamdy.aea@protonmail.com \
    --cc=info@daylightlinux.ch \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsc@kernel.org \
    --cc=sashal@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.