[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aJBcn9jb2RseRwS3@example.org>
Date: Mon, 4 Aug 2025 09:09:19 +0200
From: Alexey Gladkov <legion@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Masahiro Yamada <masahiroy@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the kbuild tree
On Mon, Aug 04, 2025 at 11:25:40AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 30 Jul 2025 16:12:23 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > After merging the kbuild tree, today's linux-next build (i386 defconfig)
> > failed like this:
> >
> > ld: .vmlinux.export.o: in function `__ksymtab___builtin_memcmp':
> > .vmlinux.export.c:(___ksymtab+__builtin_memcmp+0x0): undefined reference to `__builtin_memcmp'
> >
> > Caused by commit
> >
> > c4b487ddc51f ("modpost: Create modalias for builtin modules")
> >
> > I have reverted that commit, along with its parent and child, for
> > today. It's parent commit
> >
> > 66ef3890c628 ("modpost: Add modname to mod_device_table alias")
> >
> > generated this warning in the i386 defconfig build:
> >
> > scripts/mod/file2alias.c: In function ‘handle_moddevtable’:
> > scripts/mod/file2alias.c:1480:25: warning: variable ‘modnamelen’ set but not used [-Wunused-but-set-variable]
> > 1480 | size_t typelen, modnamelen;
> > | ^~~~~~~~~~
>
> I am still reverting those commits.
I do not have my tree. Can you apply my fix for original commit instead of
revert ?
https://lore.kernel.org/all/20250730090025.2402129-1-legion@kernel.org/
--
Rgrds, legion
Powered by blists - more mailing lists