From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [tglx-devel:genirq 29/56] ERROR: modpost: "__irq_set_lockdep_class" undefined!
Date: Fri, 11 Dec 2020 11:32:17 +0800 [thread overview]
Message-ID: <202012111114.7nT6TMM3-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git genirq
head: 53cc7c5b089bb7f673fc14f830c4a5d665812b1d
commit: 625bfc682a550bc6ab8d05a49c0204f026a66aa3 [29/56] genirq: Move irq_set_lockdep_class() to core
config: x86_64-randconfig-r015-20201209 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git/commit/?id=625bfc682a550bc6ab8d05a49c0204f026a66aa3
git remote add tglx-devel https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git
git fetch --no-tags tglx-devel genirq
git checkout 625bfc682a550bc6ab8d05a49c0204f026a66aa3
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
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: "__irq_set_lockdep_class" [drivers/pinctrl/pinctrl-single.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: 39732 bytes --]
next reply other threads:[~2020-12-11 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 3:32 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-11 3:11 [tglx-devel:genirq 29/56] ERROR: modpost: "__irq_set_lockdep_class" undefined! 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=202012111114.7nT6TMM3-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.