From: kernel test robot <lkp@intel.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: [linux-next:master 6204/6884] dm.c:undefined reference to `set_dax_nocache'
Date: Fri, 16 Feb 2024 04:37:08 +0800 [thread overview]
Message-ID: <202402160420.e4QKwoGO-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 26d7d52b6253574d5b6fec16a93e1110d1489cef
commit: 5f97767a384ee9d0e6bb37e019218efa185d6d4a [6204/6884] dm: treat alloc_dax() -EOPNOTSUPP failure as non-fatal
config: csky-randconfig-r003-20220721 (https://download.01.org/0day-ci/archive/20240216/202402160420.e4QKwoGO-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240216/202402160420.e4QKwoGO-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/202402160420.e4QKwoGO-lkp@intel.com/
All errors (new ones prefixed by >>):
csky-linux-ld: drivers/md/dm.o: in function `alloc_dev':
>> dm.c:(.text+0x35ea): undefined reference to `set_dax_nocache'
>> csky-linux-ld: dm.c:(.text+0x35f2): undefined reference to `set_dax_nomc'
>> csky-linux-ld: dm.c:(.text+0x36f0): undefined reference to `set_dax_nocache'
csky-linux-ld: dm.c:(.text+0x36f4): undefined reference to `set_dax_nomc'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-15 20:37 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=202402160420.e4QKwoGO-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-mm@kvack.org \
--cc=mathieu.desnoyers@efficios.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