From: Andrew Morton <akpm@linux-foundation.org>
To: Philip Li <philip.li@intel.com>
Cc: kernel test robot <lkp@intel.com>,
Chengkaitao <chengkaitao@kylinos.cn>,
<oe-kbuild-all@lists.linux.dev>,
David Hildenbrand <david@kernel.org>,
"Linux Memory Management List" <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-stable 72/140] arch/sparc/mm/init_64.c:2582:16: error: implicit declaration of function 'vmemmap_pgd_populate'; did you mean 'vmemmap_populate'?
Date: Tue, 24 Mar 2026 21:26:58 -0700 [thread overview]
Message-ID: <20260324212658.a267bb861af1dcbf119a1901@linux-foundation.org> (raw)
In-Reply-To: <acNdJ/q5tNB0nNjp@rli9-mobl>
On Wed, 25 Mar 2026 11:57:27 +0800 Philip Li <philip.li@intel.com> wrote:
> > The coincidence is too great. I assume Kernel Test Robot is somehow
> > treating the mm-stable differently from other branches? Can we please
> > not do that?
>
> Sorry for this "coincidence", the bot does treat all branches equally and
> there's no special handling of mm-stable. One possibility is the randconfig
> is just generated on 20260325 "sparc-randconfig-001-20260325", which is able
> to expose this issue for sparc arch.
huh, OK, thanks. I was able to reproduce it with sparc64 defconfig.
next prev parent reply other threads:[~2026-03-25 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 3:10 [akpm-mm:mm-stable 72/140] arch/sparc/mm/init_64.c:2582:16: error: implicit declaration of function 'vmemmap_pgd_populate'; did you mean 'vmemmap_populate'? kernel test robot
2026-03-25 3:27 ` Andrew Morton
2026-03-25 3:57 ` Philip Li
2026-03-25 4:26 ` Andrew Morton [this message]
2026-03-25 5:04 ` Philip Li
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=20260324212658.a267bb861af1dcbf119a1901@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chengkaitao@kylinos.cn \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=philip.li@intel.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