From: Mike Rapoport <rppt@kernel.org>
To: Liu Xinpeng <liuxp11@chinatelecom.cn>
Cc: mawupeng1@huawei.com, jrdr.linux@gmail.com, david@redhat.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] memblock tests: compiling error
Date: Wed, 27 Jul 2022 12:33:24 +0300 [thread overview]
Message-ID: <YuEGZKpXCoj7P/pV@kernel.org> (raw)
In-Reply-To: <1658889585-20778-1-git-send-email-liuxp11@chinatelecom.cn>
Hi,
On Wed, Jul 27, 2022 at 10:39:45AM +0800, Liu Xinpeng wrote:
> Subject: [PATCH v3] memblock tests: compiling error
"fix compilation errors" looks better, don't you think?
Another thing, is when you post vN of a patch please add a "patch
changelog" that describes the changes to the previous version.
I'd suggest to take a look at sections "Respond to review comments" and
"Don't get discouraged - or impatient" of the submitting patches guide.
https://kernel.org/doc/html/latest/process/submitting-patches.html
> 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'
As people pointed in v1 thread, the description on how to reproduce this is
missing.
> Fixes: 902c2d91582c ("memblock: Disable mirror feature if kernelcore is not specified")
> Fixes: 14d9a675fd0d ("mm: Ratelimited mirrored memory related warning messages")
>
> Signed-off-by: Liu Xinpeng <liuxp11@chinatelecom.cn>
> Tested-by: Ma Wupeng <mawupeng1@huawei.com>
> ---
> tools/testing/memblock/internal.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/tools/testing/memblock/internal.h b/tools/testing/memblock/internal.h
> index c2a492c05e0c..fdb7f5db7308 100644
> --- a/tools/testing/memblock/internal.h
> +++ b/tools/testing/memblock/internal.h
> @@ -9,6 +9,10 @@
> 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
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2022-07-27 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 2:39 Liu Xinpeng
2022-07-27 9:33 ` Mike Rapoport [this message]
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=YuEGZKpXCoj7P/pV@kernel.org \
--to=rppt@kernel.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=mawupeng1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox