From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 3/3] gpio: xilinx: Utilize generic bitmap_get_value and _set_value
Date: Sun, 14 Feb 2021 12:40:45 +0800 [thread overview]
Message-ID: <202102141226.pmNlFRSx-lkp@intel.com> (raw)
In-Reply-To: <1b1f706b60e4c571c4f17d53ac640e8bd8384856.1613134924.git.syednwaris@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]
Hi Syed,
I love your patch! Yet something to improve:
[auto build test ERROR on e71ba9452f0b5b2e8dc8aa5445198cd9214a6a62]
url: https://github.com/0day-ci/linux/commits/Syed-Nayyar-Waris/Introduce-the-for_each_set_clump-macro/20210212-213005
base: e71ba9452f0b5b2e8dc8aa5445198cd9214a6a62
config: i386-randconfig-d002-20200329 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/d83196ca7a23f614773c049b69ce3896679cec61
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Syed-Nayyar-Waris/Introduce-the-for_each_set_clump-macro/20210212-213005
git checkout d83196ca7a23f614773c049b69ce3896679cec61
# save the attached .config to linux build tree
make W=1 ARCH=i386
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: "bitmap_get_value" [drivers/gpio/gpio-xilinx.ko] undefined!
>> ERROR: modpost: "bitmap_set_value" [drivers/gpio/gpio-xilinx.ko] undefined!
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 33183 bytes --]
next prev parent reply other threads:[~2021-02-14 4:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 13:19 [PATCH v2 0/3] Introduce the for_each_set_clump macro Syed Nayyar Waris
2021-02-12 13:19 ` Syed Nayyar Waris
2021-02-12 13:20 ` [PATCH v2 1/3] gpiolib: " Syed Nayyar Waris
2021-02-12 13:20 ` Syed Nayyar Waris
2021-02-14 6:44 ` William Breathitt Gray
2021-02-14 6:44 ` William Breathitt Gray
2021-02-12 13:21 ` [PATCH v2 2/3] gpio: thunderx: Utilize " Syed Nayyar Waris
2021-02-12 13:21 ` Syed Nayyar Waris
2021-02-14 6:46 ` William Breathitt Gray
2021-02-14 6:46 ` William Breathitt Gray
2021-02-12 13:22 ` [PATCH v2 3/3] gpio: xilinx: Utilize generic bitmap_get_value and _set_value Syed Nayyar Waris
2021-02-12 13:22 ` Syed Nayyar Waris
2021-02-14 4:40 ` kernel test robot [this message]
2021-02-15 13:26 ` Syed Nayyar Waris
2021-02-15 13:46 ` Andy Shevchenko
2021-02-15 13:53 ` Syed Nayyar Waris
2021-02-15 15:51 ` Andy Shevchenko
2021-02-14 6:51 ` William Breathitt Gray
2021-02-14 6:51 ` William Breathitt Gray
2021-03-03 14:43 ` [PATCH v2 0/3] Introduce the for_each_set_clump macro Bartosz Golaszewski
2021-03-03 14:43 ` Bartosz Golaszewski
2021-03-06 13:39 ` Syed Nayyar Waris
2021-03-06 13:39 ` Syed Nayyar Waris
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=202102141226.pmNlFRSx-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.