From: Randy Dunlap <rdunlap@infradead.org>
To: Souptick Joarder <jrdr.linux@gmail.com>,
Liu Xinpeng <liuxp11@chinatelecom.cn>
Cc: Mike Rapoport <rppt@kernel.org>, Linux-MM <linux-mm@kvack.org>,
David Hildenbrand <david@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memblock tests: compiling error
Date: Tue, 26 Jul 2022 18:03:33 -0700 [thread overview]
Message-ID: <26b099a0-2ace-8023-7b09-f6b015f26be9@infradead.org> (raw)
In-Reply-To: <CAFqt6zabgY6DgCQBe0HCsMYScNEnKbm-0nH4ghhALZpF14rm4g@mail.gmail.com>
On 7/26/22 18:01, Souptick Joarder wrote:
> On Tue, Jul 26, 2022 at 8:35 AM Liu Xinpeng <liuxp11@chinatelecom.cn> wrote:
>>
>> memblock.o: In function `memblock_find_in_range.constprop.9':
>> memblock.c:(.text+0x4651): undefined reference to `pr_warn_ratelimited'
>> memblock.o: In function `memblock_mark_mirror':
>> memblock.c:(.text+0x7171): undefined reference to `mirrored_kernelcore'
>>
>
> what is the steps to hit this compile error ?
or what kernel .config file?
>
>> Fixs: 902c2d91582 ("memblock: Disable mirror feature if kernelcore is not
>> specified")
>> Fixs: 14d9a675fd0 ("mm: Ratelimited mirrored memory related warning")
>>
>> Signed-off-by: Liu Xinpeng <liuxp11@chinatelecom.cn>
>> ---
>> tools/testing/memblock/internal.h | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/tools/testing/memblock/internal.h b/tools/testing/memblock/internal.h
>> index c2a492c..cf67e6e 100644
>> --- a/tools/testing/memblock/internal.h
>> +++ b/tools/testing/memblock/internal.h
>> @@ -9,6 +9,9 @@
>> static int memblock_debug = 1;
>> #endif
>>
>> +#define pr_warn_ratelimited(fmt, ...) printf(fmt, ##__VA_ARGS__);
>> +
>> +bool mirrored_kernelcore = false;
>> struct page {};
>>
>> void memblock_free_pages(struct page *page, unsigned long pfn,
>> --
>> 1.8.3.1
>>
>>
--
~Randy
next prev parent reply other threads:[~2022-07-27 1:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 3:05 Liu Xinpeng
2022-07-27 1:01 ` Souptick Joarder
2022-07-27 1:03 ` Randy Dunlap [this message]
2022-07-27 1:53 ` mawupeng
2022-07-27 1:53 ` mawupeng
2022-07-27 2:06 ` liuxp11
2022-07-27 2:20 ` Kefeng Wang
2022-07-26 3:21 Liu Xinpeng
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=26b099a0-2ace-8023-7b09-f6b015f26be9@infradead.org \
--to=rdunlap@infradead.org \
--cc=david@redhat.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuxp11@chinatelecom.cn \
--cc=rppt@kernel.org \
/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