All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [xilinx-xlnx:xlnx_rebase_v6.18 765/871] mtd_virt_concat.c:(.exit.text+0x0): multiple definition of `cleanup_module'; drivers/mtd/mtdcore.o:mtdcore.c:(.exit.text+0x0): first defined here
Date: Sat, 16 May 2026 22:43:03 +0800	[thread overview]
Message-ID: <202605162231.dvgcqSjR-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "only suspicious fbc files changed"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: git@amd.com
TO: Michal Simek <monstr@monstr.eu>

tree:   https://github.com/Xilinx/linux-xlnx xlnx_rebase_v6.18
head:   8ad23fcb26beeb807a7f0f3341137ec98e93f390
commit: 57335cb7376d59e7c4946a731db22867c7809203 [765/871] mtd: fix modpost errors for mtd_virt_concat symbols
:::::: branch date: 9 days ago
:::::: commit date: 5 weeks ago
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20260516/202605162231.dvgcqSjR-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260516/202605162231.dvgcqSjR-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/r/202605162231.dvgcqSjR-lkp@intel.com/

All errors (new ones prefixed by >>):

   m68k-linux-ld: drivers/mtd/mtd_virt_concat.o: in function `mtd_virt_concat_exit':
>> mtd_virt_concat.c:(.exit.text+0x0): multiple definition of `cleanup_module'; drivers/mtd/mtdcore.o:mtdcore.c:(.exit.text+0x0): first defined here

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-05-16 14:43 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=202605162231.dvgcqSjR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.