From: Matija Glavinic Pecotic <matija.glavinic-pecotic.ext@nokia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Russell King <linux@armlinux.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"kernelci.org bot" <bot@kernelci.org>
Subject: Re: linux-next: build failure after merge of the arm tree
Date: Wed, 31 Aug 2022 11:14:33 +0200 [thread overview]
Message-ID: <fd5e6961-5809-a125-f909-3cfdff90ef35@nokia.com> (raw)
In-Reply-To: <20220831191055.16f85948@canb.auug.org.au>
Hi,
On 31.08.2022 11:10, Stephen Rothwell wrote:
> After merging the arm tree, today's linux-next build (quite a few
> including arm allnoconfig clang-16, arm allnoconfig gcc-10) failed
> like this:
>
> ld.lld: error: undefined symbol: phys_initrd_start
> or
> init.c:(.init.text+0xd4): undefined reference to `phys_initrd_start'
>
> Caused by commit
>
> b35b2736b43d ("ARM: 9230/1: Support initrd with address in boot alias region")
my apologies for that, I missed to test with CONFIG_BLK_DEV_INITRD=n
I've seen Russell dropping patch already, hopefully update will
soon follow.
Regards,
Matija
next prev parent reply other threads:[~2022-08-31 9:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 9:10 linux-next: build failure after merge of the arm tree Stephen Rothwell
2022-08-31 9:14 ` Matija Glavinic Pecotic [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-03 0:15 Stephen Rothwell
2024-05-03 8:18 ` Russell King (Oracle)
2024-05-03 8:23 ` Russell King (Oracle)
2024-05-03 12:08 ` Stephen Rothwell
2024-05-03 12:29 ` Russell King (Oracle)
2021-10-25 23:25 Stephen Rothwell
2020-01-19 21:24 Stephen Rothwell
2020-01-19 21:31 ` Stephen Rothwell
2020-01-19 22:02 ` Russell King - ARM Linux admin
2017-04-20 22:40 Stephen Rothwell
2017-04-21 7:58 ` Mason
2017-04-21 8:12 ` Stephen Rothwell
2017-04-21 8:30 ` Mason
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-22 8:41 ` Mason
2017-04-24 4:20 ` Vinod Koul
2017-06-14 19:23 ` Mason
2017-04-21 11:27 ` Mason
2015-05-29 1:09 Stephen Rothwell
2014-04-10 1:35 Stephen Rothwell
2011-03-02 14:13 Stephen Rothwell
2011-03-02 15:55 ` Nicolas Pitre
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=fd5e6961-5809-a125-f909-3cfdff90ef35@nokia.com \
--to=matija.glavinic-pecotic.ext@nokia.com \
--cc=bot@kernelci.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).