From: kernel test robot <lkp@intel.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>
Subject: [akpm-mm:mm-nonmm-unstable 82/133] fdt.c:(.text+0x6ac): multiple definition of `kho_alloc_preserve'; mm/mm_init.o:mm_init.c:(.text+0x0): first defined here
Date: Sun, 16 Nov 2025 03:17:18 +0800 [thread overview]
Message-ID: <202511160302.QiMsgMfT-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
head: 4fc88c237bfe11bde443e104428aac56e63a997f
commit: 88316955b5b1b4cb0cb2fad416f7e8dde9b246a0 [82/133] kho: introduce high-level memory allocation API
config: arc-allnoconfig (https://download.01.org/0day-ci/archive/20251116/202511160302.QiMsgMfT-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251116/202511160302.QiMsgMfT-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/202511160302.QiMsgMfT-lkp@intel.com/
All errors (new ones prefixed by >>):
arc-linux-ld: drivers/of/fdt.o: in function `kho_alloc_preserve':
>> fdt.c:(.text+0x6ac): multiple definition of `kho_alloc_preserve'; mm/mm_init.o:mm_init.c:(.text+0x0): first defined here
arc-linux-ld: drivers/of/fdt.o: in function `kho_unpreserve_free':
>> fdt.c:(.text+0x6b4): multiple definition of `kho_unpreserve_free'; mm/mm_init.o:mm_init.c:(.text+0x8): first defined here
arc-linux-ld: drivers/of/fdt.o: in function `kho_restore_free':
>> fdt.c:(.text+0x6b8): multiple definition of `kho_restore_free'; mm/mm_init.o:mm_init.c:(.text+0xc): first defined here
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-15 19:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202511160302.QiMsgMfT-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
/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