From: Mike Rapoport <rppt@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
Wang Kefeng <wangkefeng.wang@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Matija Glavinic Pecotic <matija.glavinic-pecotic.ext@nokia.com>,
Victor Hassan <victor@allwinnertech.com>
Subject: Re: arch/arm/mm/init.o: in function `arm_memblock_init': init.c:(.init.text+0xc8): undefined reference to `phys_initrd_start'
Date: Wed, 31 Aug 2022 13:54:45 +0300 [thread overview]
Message-ID: <Yw899e/S6wuo4EX6@kernel.org> (raw)
In-Reply-To: <CA+G9fYt6831htScyAHTk9w1PMLU-kLPvQRqJt73t9=NHLM5qOA@mail.gmail.com>
On Wed, Aug 31, 2022 at 02:26:36PM +0530, Naresh Kamboju wrote:
> The following arm builds failed on Linux next-20220831.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Regressions found on arm:
> - build-clang-14-allnoconfig
> - build-gcc-11-tinyconfig
> - build-clang-11-tinyconfig
> - build-gcc-9-tinyconfig
> - build-gcc-11-orion5x_defconfig
> - build-gcc-10-allnoconfig
> - build-clang-nightly-orion5x_defconfig
> - build-gcc-8-orion5x_defconfig
> - build-clang-11-allnoconfig
> - build-gcc-8-tinyconfig
> - build-clang-11-orion5x_defconfig
> - build-clang-nightly-tinyconfig
> - build-clang-13-allnoconfig
> - build-gcc-9-allnoconfig
> - build-clang-13-tinyconfig
> - build-clang-14-orion5x_defconfig
> - build-clang-13-orion5x_defconfig
> - build-clang-14-tinyconfig
> - build-gcc-8-allnoconfig
> - build-gcc-9-orion5x_defconfig
> - build-clang-12-tinyconfig
> - build-clang-nightly-allnoconfig
> - build-gcc-10-orion5x_defconfig
> - build-clang-12-orion5x_defconfig
> - build-gcc-10-tinyconfig
> - build-clang-12-allnoconfig
> - build-gcc-11-allnoconfig
>
> Build error:
> ------------
> arm-linux-gnueabihf-ld: arch/arm/mm/init.o: in function `arm_memblock_init':
> init.c:(.init.text+0xc8): undefined reference to `phys_initrd_start'
> make[1]: *** [/builds/linux/Makefile:1250: vmlinux] Error 1
Looks like this is because of
Fixes: b35b2736b43d ("ARM: 9230/1: Support initrd with address in boot alias region")
that uses phys_initrd_start regardless of CONFIG_BLK_DEV_INITRD
> Build log link:
> https://builds.tuxbuild.com/2E6pMzczzw7tLMxz7WFjaPgQ9Io/
>
> Steps to reproduce:
> -------------------
> # To install tuxmake on your system globally:
> # sudo pip3 install -U tuxmake
>
> tuxmake --runtime podman --target-arch arm --toolchain gcc-11 --kconfig
> tinyconfig
>
> --
> Linaro LKFT
> https://lkft.linaro.org
--
Sincerely yours,
Mike.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
Wang Kefeng <wangkefeng.wang@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Matija Glavinic Pecotic <matija.glavinic-pecotic.ext@nokia.com>,
Victor Hassan <victor@allwinnertech.com>
Subject: Re: arch/arm/mm/init.o: in function `arm_memblock_init': init.c:(.init.text+0xc8): undefined reference to `phys_initrd_start'
Date: Wed, 31 Aug 2022 13:54:45 +0300 [thread overview]
Message-ID: <Yw899e/S6wuo4EX6@kernel.org> (raw)
In-Reply-To: <CA+G9fYt6831htScyAHTk9w1PMLU-kLPvQRqJt73t9=NHLM5qOA@mail.gmail.com>
On Wed, Aug 31, 2022 at 02:26:36PM +0530, Naresh Kamboju wrote:
> The following arm builds failed on Linux next-20220831.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Regressions found on arm:
> - build-clang-14-allnoconfig
> - build-gcc-11-tinyconfig
> - build-clang-11-tinyconfig
> - build-gcc-9-tinyconfig
> - build-gcc-11-orion5x_defconfig
> - build-gcc-10-allnoconfig
> - build-clang-nightly-orion5x_defconfig
> - build-gcc-8-orion5x_defconfig
> - build-clang-11-allnoconfig
> - build-gcc-8-tinyconfig
> - build-clang-11-orion5x_defconfig
> - build-clang-nightly-tinyconfig
> - build-clang-13-allnoconfig
> - build-gcc-9-allnoconfig
> - build-clang-13-tinyconfig
> - build-clang-14-orion5x_defconfig
> - build-clang-13-orion5x_defconfig
> - build-clang-14-tinyconfig
> - build-gcc-8-allnoconfig
> - build-gcc-9-orion5x_defconfig
> - build-clang-12-tinyconfig
> - build-clang-nightly-allnoconfig
> - build-gcc-10-orion5x_defconfig
> - build-clang-12-orion5x_defconfig
> - build-gcc-10-tinyconfig
> - build-clang-12-allnoconfig
> - build-gcc-11-allnoconfig
>
> Build error:
> ------------
> arm-linux-gnueabihf-ld: arch/arm/mm/init.o: in function `arm_memblock_init':
> init.c:(.init.text+0xc8): undefined reference to `phys_initrd_start'
> make[1]: *** [/builds/linux/Makefile:1250: vmlinux] Error 1
Looks like this is because of
Fixes: b35b2736b43d ("ARM: 9230/1: Support initrd with address in boot alias region")
that uses phys_initrd_start regardless of CONFIG_BLK_DEV_INITRD
> Build log link:
> https://builds.tuxbuild.com/2E6pMzczzw7tLMxz7WFjaPgQ9Io/
>
> Steps to reproduce:
> -------------------
> # To install tuxmake on your system globally:
> # sudo pip3 install -U tuxmake
>
> tuxmake --runtime podman --target-arch arm --toolchain gcc-11 --kconfig
> tinyconfig
>
> --
> Linaro LKFT
> https://lkft.linaro.org
--
Sincerely yours,
Mike.
next parent reply other threads:[~2022-08-31 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+G9fYt6831htScyAHTk9w1PMLU-kLPvQRqJt73t9=NHLM5qOA@mail.gmail.com>
2022-08-31 10:54 ` Mike Rapoport [this message]
2022-08-31 10:54 ` arch/arm/mm/init.o: in function `arm_memblock_init': init.c:(.init.text+0xc8): undefined reference to `phys_initrd_start' Mike Rapoport
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=Yw899e/S6wuo4EX6@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=matija.glavinic-pecotic.ext@nokia.com \
--cc=naresh.kamboju@linaro.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=victor@allwinnertech.com \
--cc=wangkefeng.wang@huawei.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 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.