From: kernel test robot <lkp@intel.com>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Linus Walleij <linus.walleij@linaro.org>,
Jonas Gorski <jonas.gorski@gmail.com>
Subject: [linux-next:master 7883/8451] pinctrl-bcm6328.c:undefined reference to `pinconf_generic_dt_node_to_map'
Date: Wed, 31 Mar 2021 01:04:02 +0800 [thread overview]
Message-ID: <202103310156.F6bbxg1C-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4143e05b7b171902f4938614c2a68821e1af46bc
commit: 9bf34ac5ab5805f0a798d40423c05596b7a0cee6 [7883/8451] pinctrl: add a pincontrol driver for BCM6328
config: m68k-randconfig-r036-20210330 (attached as .config)
compiler: m68k-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9bf34ac5ab5805f0a798d40423c05596b7a0cee6
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 9bf34ac5ab5805f0a798d40423c05596b7a0cee6
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k
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 >>):
m68k-linux-ld: drivers/pinctrl/bcm/pinctrl-bcm6328.o: in function `pinconf_generic_dt_node_to_map_pin':
>> pinctrl-bcm6328.c:(.text+0xb6): undefined reference to `pinconf_generic_dt_node_to_map'
---
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: 23666 bytes --]
reply other threads:[~2021-03-30 17:05 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=202103310156.F6bbxg1C-lkp@intel.com \
--to=lkp@intel.com \
--cc=jonas.gorski@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mm@kvack.org \
--cc=noltari@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox