From: kernel test robot <lkp@intel.com>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [linux-next:master 2500/12695] ERROR: modpost: "iio_triggered_buffer_cleanup" [drivers/iio/dummy/iio_dummy.ko] undefined!
Date: Thu, 15 Apr 2021 11:21:27 +0800 [thread overview]
Message-ID: <202104151124.wFBJHgBa-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 1c8ce959b41a18b9657eaafd7a1215a8da67d3ab
commit: 738f6ba1180046904402ffbe210fbd2fa2c4b050 [2500/12695] iio: dummy: iio_simple_dummy_buffer: use triggered buffer core calls
config: um-randconfig-r025-20210414 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=738f6ba1180046904402ffbe210fbd2fa2c4b050
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 738f6ba1180046904402ffbe210fbd2fa2c4b050
# save the attached .config to linux build tree
make W=1 W=1 ARCH=um
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "iio_triggered_buffer_cleanup" [drivers/iio/dummy/iio_dummy.ko] undefined!
>> ERROR: modpost: "iio_triggered_buffer_setup_ext" [drivers/iio/dummy/iio_dummy.ko] undefined!
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 11053 bytes --]
reply other threads:[~2021-04-15 3:21 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=202104151124.wFBJHgBa-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alexandru.ardelean@analog.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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