From: Randy Dunlap <rdunlap@infradead.org>
To: broonie@kernel.org, Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Sep 28 (mm/memory-failure.c)
Date: Wed, 28 Sep 2022 22:21:29 -0700 [thread overview]
Message-ID: <6dd6222c-c1d4-a7fe-4e4a-87bf7ac3616d@infradead.org> (raw)
In-Reply-To: <20220928192605.247546-1-broonie@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
On 9/28/22 12:26, broonie@kernel.org wrote:
> Hi all,
>
> Changes since 20220927:
>
on i386 or x86_64, when
CONFIG_MEMORY_FAILURE=y and CONFIG_MEMORY_HOTPLUG is not set,
because drivers/base/memory.c is not built at all:
ld: mm/memory-failure.o: in function `num_poisoned_pages_inc':
mm/memory-failure.c:80: undefined reference to `memblk_nr_poison_inc'
ld: mm/memory-failure.c:80: undefined reference to `memblk_nr_poison_inc'
ld: mm/memory-failure.c:80: undefined reference to `memblk_nr_poison_inc'
ld: mm/memory-failure.c:80: undefined reference to `memblk_nr_poison_inc'
ld: mm/memory-failure.c:80: undefined reference to `memblk_nr_poison_inc'
ld: mm/memory-failure.o:mm/memory-failure.c:80: more undefined references to `memblk_nr_poison_inc' follow
ld: mm/memory-failure.o: in function `num_poisoned_pages_sub':
mm/memory-failure.c:87: undefined reference to `memblk_nr_poison_sub'
Full randconfig file is attached (for x86_64).
--
~Randy
[-- Attachment #2: config-r6241.gz --]
[-- Type: application/gzip, Size: 42736 bytes --]
next prev parent reply other threads:[~2022-09-29 5:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 19:26 linux-next: Tree for Sep 28 broonie
2022-09-29 5:21 ` Randy Dunlap [this message]
2022-09-29 5:59 ` linux-next: Tree for Sep 28 (Kconfig: SND_SOC_QDSP6) Randy Dunlap
2022-09-29 6:09 ` linux-next: Tree for Sep 28 (drivers/gpu/drm/msm/msm_gem_shrinker.c) Randy Dunlap
2022-09-29 7:09 ` Geert Uytterhoeven
2022-09-29 15:05 ` Rob Clark
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=6dd6222c-c1d4-a7fe-4e4a-87bf7ac3616d@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=naoya.horiguchi@nec.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;
as well as URLs for NNTP newsgroup(s).