From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Muchun Song <songmuchun@bytedance•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
X86 ML <x86@kernel•org>
Subject: Re: linux-next: Tree for Mar 15 (arch/x86/mm/init_64.c :: vmemmap)
Date: Mon, 15 Mar 2021 09:05:25 -0700 [thread overview]
Message-ID: <bebcf210-e0a4-31d5-5c56-38643ce77ec4@infradead.org> (raw)
In-Reply-To: <20210315162428.3719edb2@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
On 3/14/21 10:24 PM, Stephen Rothwell wrote:
> Hi all,
>
> Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> so please be careful if you are trying to bisect a bug.
>
> News: if your -next included tree is based on Linus' tree tag
> v5.12-rc1{,-dontuse} (or somewhere between v5.11 and that tag), please
> consider rebasing it onto v5.12-rc2. Also, please check any branches
> merged into your branch.
>
> Changes since 20210312:
>
on x86_64:
In file included from ../include/asm-generic/bug.h:5:0,
from ../arch/x86/include/asm/bug.h:93,
from ../include/linux/bug.h:5,
from ../include/linux/signal.h:5,
from ../arch/x86/mm/init_64.c:10:
../arch/x86/mm/init_64.c: In function ‘remove_pmd_table’:
../arch/x86/mm/init_64.c:1127:8: error: implicit declaration of function ‘vmemmap_pmd_is_unused’; did you mean ‘vmemmap_pmd_populate’? [-Werror=implicit-function-declaration]
vmemmap_pmd_is_unused(addr, next)) {
^
../include/linux/compiler.h:58:52: note: in definition of macro ‘__trace_if_var’
#define __trace_if_var(cond) (__builtin_constant_p(cond) ? (cond) : __trace_if_value(cond))
^~~~
../arch/x86/mm/init_64.c:1126:11: note: in expansion of macro ‘if’
} else if (IS_ENABLED(CONFIG_SPARSEMEM_VMEMMAP) &&
^~
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead•org>
[-- Attachment #2: config-r8237.gz --]
[-- Type: application/gzip, Size: 52006 bytes --]
next prev parent reply other threads:[~2021-03-15 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 5:24 linux-next: Tree for Mar 15 Stephen Rothwell
2021-03-15 16:05 ` Randy Dunlap [this message]
2021-03-16 2:56 ` [External] Re: linux-next: Tree for Mar 15 (arch/x86/mm/init_64.c :: vmemmap) Muchun Song
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=bebcf210-e0a4-31d5-5c56-38643ce77ec4@infradead.org \
--to=rdunlap@infradead$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=songmuchun@bytedance$(echo .)com \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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