From: kernel test robot <lkp@intel.com>
To: Ruidong Tian <tianruidong@linux.alibaba.com>, <pjw@kernel.org>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>, <alex@ghiti.fr>
Cc: <oe-kbuild-all@lists.linux.dev>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<zhuo.song@linux.alibaba.com>, <oliver.yang@linux.alibaba.com>,
Ruidong Tian <tianruidong@linux.alibaba.com>
Subject: Re: [PATCH] riscv: add copy_mc_to_{kernel,user} support to enable MC fault tolerance
Date: Thu, 14 May 2026 22:09:05 +0800 [thread overview]
Message-ID: <agXXgcLJbPWeSfBi@rli9-mobl> (raw)
In-Reply-To: <20260508062439.3000014-1-tianruidong@linux.alibaba.com>
Hi Ruidong,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.16-rc1 next-20260508]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ruidong-Tian/riscv-add-copy_mc_to_-kernel-user-support-to-enable-MC-fault-tolerance/20260514-020843
base: linus/master
patch link: https://lore.kernel.org/r/20260508062439.3000014-1-tianruidong%40linux.alibaba.com
patch subject: [PATCH] riscv: add copy_mc_to_{kernel,user} support to enable MC fault tolerance
config: riscv-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260514/202605140846.VOAZjcrL-lkp@intel.com/config)
compiler: riscv64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260514/202605140846.VOAZjcrL-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/202605140846.VOAZjcrL-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "memcpy_mc" [drivers/nvdimm/libnvdimm.ko] undefined!
>> ERROR: modpost: "memcpy_mc" [drivers/nvdimm/nd_pmem.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Ruidong Tian <tianruidong@linux.alibaba.com>, <pjw@kernel.org>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>, <alex@ghiti.fr>
Cc: <oe-kbuild-all@lists.linux.dev>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<zhuo.song@linux.alibaba.com>, <oliver.yang@linux.alibaba.com>,
Ruidong Tian <tianruidong@linux.alibaba.com>
Subject: Re: [PATCH] riscv: add copy_mc_to_{kernel,user} support to enable MC fault tolerance
Date: Thu, 14 May 2026 22:09:05 +0800 [thread overview]
Message-ID: <agXXgcLJbPWeSfBi@rli9-mobl> (raw)
In-Reply-To: <20260508062439.3000014-1-tianruidong@linux.alibaba.com>
Hi Ruidong,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.16-rc1 next-20260508]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ruidong-Tian/riscv-add-copy_mc_to_-kernel-user-support-to-enable-MC-fault-tolerance/20260514-020843
base: linus/master
patch link: https://lore.kernel.org/r/20260508062439.3000014-1-tianruidong%40linux.alibaba.com
patch subject: [PATCH] riscv: add copy_mc_to_{kernel,user} support to enable MC fault tolerance
config: riscv-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260514/202605140846.VOAZjcrL-lkp@intel.com/config)
compiler: riscv64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260514/202605140846.VOAZjcrL-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/202605140846.VOAZjcrL-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "memcpy_mc" [drivers/nvdimm/libnvdimm.ko] undefined!
>> ERROR: modpost: "memcpy_mc" [drivers/nvdimm/nd_pmem.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-05-14 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 6:24 [PATCH] riscv: add copy_mc_to_{kernel,user} support to enable MC fault tolerance Ruidong Tian
2026-05-08 6:24 ` Ruidong Tian
2026-05-14 14:09 ` kernel test robot [this message]
2026-05-14 14:09 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2026-05-14 7:04 kernel test robot
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=agXXgcLJbPWeSfBi@rli9-mobl \
--to=lkp@intel.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oliver.yang@linux.alibaba.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=tianruidong@linux.alibaba.com \
--cc=zhuo.song@linux.alibaba.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 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.