From: Edward Cree <ecree.xilinx@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Jakub Kicinski <kuba@kernel.org>,
Simon Horman <simon.horman@corigine.com>,
Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@amd.com>,
"linux-net-drivers@amd.com" <linux-net-drivers@amd.com>
Subject: Re: [linux-next:master 8214/10326] drivers/net/ethernet/sfc/tc_encap_actions.c:277: undefined reference to `ip_send_check'
Date: Thu, 15 Jun 2023 15:44:14 +0100 [thread overview]
Message-ID: <a80867f3-a2b1-3ffb-d7b1-784e4bb94163@gmail.com> (raw)
In-Reply-To: <202306151656.yttECVTP-lkp@intel.com>
On 15/06/2023 09:50, kernel test robot wrote:
> config: riscv-buildonly-randconfig-r001-20230614 (https://download.01.org/0day-ci/archive/20230615/202306151656.yttECVTP-lkp@intel.com/config)
This has:
# CONFIG_INET is not set
> All errors (new ones prefixed by >>):
>
> riscv32-linux-ld: drivers/net/ethernet/sfc/tc_encap_actions.o: in function `.L0 ':
>>> drivers/net/ethernet/sfc/tc_encap_actions.c:277: undefined reference to `ip_send_check'
> riscv32-linux-ld: drivers/net/ethernet/sfc/tc_encap_actions.o: in function `.L0 ':
> include/linux/rhashtable.h:648: undefined reference to `arp_tbl'
> riscv32-linux-ld: drivers/net/ethernet/sfc/tc_encap_actions.o: in function `.L0 ':
> drivers/net/ethernet/sfc/tc_encap_actions.c:135: undefined reference to `ip_route_output_flow'
From which these errors follow, since these symbols are in net/ipv4/*.o.
Not sure whether to put ifdefs in tc_encap_actions.c, or just make
CONFIG_SFC[_SRIOV?] depend on (or select?) CONFIG_INET. Because is
there really a use case for putting an sfc NIC in a box without IP?
-ed
next prev parent reply other threads:[~2023-06-15 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 8:50 kernel test robot
2023-06-15 14:44 ` Edward Cree [this message]
2023-06-15 15:32 ` Jakub Kicinski
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=a80867f3-a2b1-3ffb-d7b1-784e4bb94163@gmail.com \
--to=ecree.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-net-drivers@amd.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pieter.jansen-van-vuuren@amd.com \
--cc=simon.horman@corigine.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