[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3f5ec5dd-8388-13b9-3f22-43505922c561@infradead.org>
Date: Mon, 24 Feb 2020 22:21:19 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>, broonie@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-next@...r.kernel.org, mhocko@...e.cz,
mm-commits@...r.kernel.org, sfr@...b.auug.org.au,
Masami Hiramatsu <mhiramat@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: mmotm 2020-02-24-19-53 uploaded (init/main.c: initrd*)
On 2/24/20 10:18 PM, Randy Dunlap wrote:
> On 2/24/20 10:16 PM, Randy Dunlap wrote:
>> On 2/24/20 7:53 PM, Andrew Morton wrote:
>>> The mm-of-the-moment snapshot 2020-02-24-19-53 has been uploaded to
>>>
>>> http://www.ozlabs.org/~akpm/mmotm/
>>>
>>> mmotm-readme.txt says
>>>
>>> README for mm-of-the-moment:
>>>
>>> http://www.ozlabs.org/~akpm/mmotm/
>>>
>>> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
>>> more than once a week.
>>>
>>
>> (I don't see what patch is causing this)
>>
>
> It appears to be related to BOOTCONFIG.
>
Argh. My bad. This build error happens in linux-next-20200225, not mmotm.
>>
>> on i386:
>> # CONFIG_BLK_DEV_INITRD is not set
>>
>>
>> ld: init/main.o: in function `start_kernel':
>> main.c:(.init.text+0x7c8): undefined reference to `initrd_end'
>> ld: main.c:(.init.text+0x803): undefined reference to `initrd_start'
>>
>>
>> Full randconfig file is attached.
>>
>
>
--
~Randy
Reported-by: Randy Dunlap <rdunlap@...radead.org>
Powered by blists - more mailing lists