linux-kernel - Re: linux-next: build failure after merge of the gpio-brgl tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Fri, 23 Feb 2024 08:51:10 +0100
From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Bartosz Golaszewski <brgl@...ev.pl>, Andy Shevchenko <andy.shevchenko@...il.com>, 
	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 gpio-brgl tree

On Fri, 23 Feb 2024 at 04:33, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> After merging the gpio-brgl tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> x86_64-linux-gnu-ld: vmlinux.o: in function `bgpio_write64':
> gpio-mmio.c:(.text+0x1489427): undefined reference to `iowrite64'
> x86_64-linux-gnu-ld: vmlinux.o: in function `bgpio_read64':
> gpio-mmio.c:(.text+0x14894a0): undefined reference to `ioread64'
> x86_64-linux-gnu-ld: vmlinux.o: in function `bgpio_write64be':
> gpio-mmio.c:(.text+0x1489527): undefined reference to `iowrite64be'
> x86_64-linux-gnu-ld: vmlinux.o: in function `bgpio_read64be':
> gpio-mmio.c:(.text+0x14895a0): undefined reference to `ioread64be'
>
> Caused by commit
>
>   36e44186e0ba ("gpio: mmio: Support 64-bit BE access")
>
> I have used the gpio-brgl from next-20240222 for today.
>
> --
> Cheers,
> Stephen Rothwell

Hi Stephen,

I'm not seeing this issue with allmodconfig on x86_64, could you give
me some more information on the build environment?

Andy: Could it be that the ifdefs you added should depend on
CONFIG_64BIT and not only on the BITS_PER_LONG value?

Bartosz