From: kernel test robot <lkp@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 9707/11436] lcs.c:undefined reference to `fddi_type_trans'
Date: Wed, 21 Jun 2023 17:44:09 +0800 [thread overview]
Message-ID: <202306211734.nx6uUSBS-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 15e71592dbae49a674429c618a10401d7f992ac3
commit: 1282723361209d06fb1466ffb90e63b1161320b6 [9707/11436] s390/net: lcs: use IS_ENABLED() for kconfig detection
config: s390-randconfig-r036-20230620 (https://download.01.org/0day-ci/archive/20230621/202306211734.nx6uUSBS-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20230621/202306211734.nx6uUSBS-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202306211734.nx6uUSBS-lkp@intel.com/
All errors (new ones prefixed by >>):
s390x-linux-ld: drivers/net/ethernet/sfc/ef100_netdev.o: in function `ef100_netdev_event':
ef100_netdev.c:(.text+0x134): undefined reference to `efx_tc_netdev_event'
s390x-linux-ld: drivers/net/ethernet/sfc/ef100_netdev.o: in function `ef100_netevent_event':
ef100_netdev.c:(.text+0x89a): undefined reference to `efx_tc_netevent_event'
s390x-linux-ld: drivers/s390/net/lcs.o: in function `lcs_new_device':
>> lcs.c:(.text+0xe26): undefined reference to `fddi_type_trans'
>> s390x-linux-ld: lcs.c:(.text+0xe36): undefined reference to `alloc_fddidev'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-21 9:45 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=202306211734.nx6uUSBS-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rdunlap@infradead.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