From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>,
broonie@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: mmotm 2020-02-24-19-53 uploaded (init/main.c: initrd*)
Date: Mon, 24 Feb 2020 22:21:19 -0800 [thread overview]
Message-ID: <3f5ec5dd-8388-13b9-3f22-43505922c561@infradead.org> (raw)
In-Reply-To: <fb37122d-c787-fb1f-10e6-a0795ef91b71@infradead.org>
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@infradead.org>
next prev parent reply other threads:[~2020-02-25 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200203173311.6269a8be06a05e5a4aa08a93@linux-foundation.org>
2020-02-14 6:26 ` mmotm 2020-02-13-22-26 uploaded Andrew Morton
[not found] ` <8e1e8f6e-0da1-e9e0-fa1b-bfd792256604@infradead.org>
2020-02-14 17:18 ` mmotm 2020-02-13-22-26 uploaded (mm/hugetlb.c) Mike Kravetz
2020-02-14 20:51 ` Mina Almasry
2020-02-25 3:53 ` mmotm 2020-02-24-19-53 uploaded Andrew Morton
[not found] ` <ba775044-c408-23d3-998d-38fd59d4face@infradead.org>
2020-02-25 6:18 ` mmotm 2020-02-24-19-53 uploaded (init/main.c: initrd*) Randy Dunlap
2020-02-25 6:21 ` Randy Dunlap [this message]
[not found] ` <c15a7c7e-df7c-8a30-0bb1-03f8b04b7be5@infradead.org>
2020-02-27 21:52 ` mmotm 2020-02-24-19-53 uploaded (objtool warning) Josh Poimboeuf
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=3f5ec5dd-8388-13b9-3f22-43505922c561@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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).