From: kernel test robot <lkp@intel.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [saeed:net-next-mlx4 36/89] undefined reference to `ipv6_mc_check_mld'
Date: Wed, 9 Feb 2022 06:09:09 +0800 [thread overview]
Message-ID: <202202090647.RlBrHxf1-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git net-next-mlx4
head: c3e676b98326a419f30dd5d956c68fc33323f4fd
commit: 47aeea0d57e80c9449448802aede54526a3d6305 [36/89] net: lan966x: Implement the callback SWITCHDEV_ATTR_ID_BRIDGE_MC_DISABLED
config: parisc-randconfig-r012-20220208 (https://download.01.org/0day-ci/archive/20220209/202202090647.RlBrHxf1-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 11.2.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/saeed/linux.git/commit/?id=47aeea0d57e80c9449448802aede54526a3d6305
git remote add saeed https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git
git fetch --no-tags saeed net-next-mlx4
git checkout 47aeea0d57e80c9449448802aede54526a3d6305
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=parisc SHELL=/bin/bash
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 >>):
hppa-linux-ld: drivers/net/ethernet/microchip/lan966x/lan966x_main.o: in function `lan966x_xtr_irq_handler.part.0':
>> (.text+0x2240): undefined reference to `ipv6_mc_check_mld'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-08 22:29 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=202202090647.RlBrHxf1-lkp@intel.com \
--to=lkp@intel.com \
--cc=horatiu.vultur@microchip.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®