From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: 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 20:27:54 -0700 [thread overview]
Message-ID: <20260324202754.6f29c4f6530ec7ea9d1f753d@linux-foundation.org> (raw)
In-Reply-To: <202603251147.CtgepAeH-lkp@intel.com>
On Wed, 25 Mar 2026 11:10:49 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-stable
> head: e393ce79b3cf63c2810be882eb6e531a54f520f4
> commit: e504282091c8e4dc4f945c89d9b44ac2e0bfe504 [72/140] mm: convert vmemmap_p?d_populate() to static functions
> config: sparc-randconfig-001-20260325 (https://download.01.org/0day-ci/archive/20260325/202603251147.CtgepAeH-lkp@intel.com/config)
> compiler: sparc64-linux-gcc (GCC) 8.5.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260325/202603251147.CtgepAeH-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202603251147.CtgepAeH-lkp@intel.com/
>
> All error/warnings (new ones prefixed by >>):
>
> arch/sparc/mm/init_64.c: In function 'sun4v_linear_pte_xor_finalize':
> arch/sparc/mm/init_64.c:2202:16: warning: variable 'pagecv_flag' set but not used [-Wunused-but-set-variable]
> unsigned long pagecv_flag;
> ^~~~~~~~~~~
> arch/sparc/mm/init_64.c: In function 'vmemmap_populate':
> >> arch/sparc/mm/init_64.c:2582:16: error: implicit declaration of function 'vmemmap_pgd_populate'; did you mean 'vmemmap_populate'? [-Werror=implicit-function-declaration]
> pgd_t *pgd = vmemmap_pgd_populate(vstart, node);
> ^~~~~~~~~~~~~~~~~~~~
Oh fecal matter. Seven weeks in mm.git and then seven milliseconds
after I move it into mm-stable, we get this.
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?
Thanks, I dropped the patch. Chengkaitao, please redo and resend after
7.1-rc1.
next prev parent reply other threads:[~2026-03-25 3:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 3:10 kernel test robot
2026-03-25 3:27 ` Andrew Morton [this message]
2026-03-25 3:57 ` Philip Li
2026-03-25 4:26 ` Andrew Morton
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=20260324202754.6f29c4f6530ec7ea9d1f753d@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 \
/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