From: Simon Horman <simon.horman@corigine.com>
To: Edward Cree <ecree.xilinx@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jakub Kicinski <kuba@kernel.org>,
Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@amd.com>
Subject: Re: [netdev-net-next:main 26/28] ld.lld: error: undefined symbol: efx_tc_netdev_event
Date: Tue, 13 Jun 2023 07:50:16 +0200 [thread overview]
Message-ID: <ZIgDmJ9kgsfbZHm4@corigine.com> (raw)
In-Reply-To: <8724de62-fe9b-cdd4-bb39-b3c06b440f5f@gmail.com>
On Mon, Jun 12, 2023 at 09:44:45PM +0100, Edward Cree wrote:
> On 12/06/2023 09:15, Simon Horman wrote:
> > On Sat, Jun 10, 2023 at 09:10:45PM +0800, kernel test robot wrote:
> >> All errors (new ones prefixed by >>):
> >>
> >>>> ld.lld: error: undefined symbol: efx_tc_netdev_event
> >> >>> referenced by ef100_netdev.c:313 (drivers/net/ethernet/sfc/ef100_netdev.c:313)
> >> >>> drivers/net/ethernet/sfc/ef100_netdev.o:(ef100_netdev_event) in archive vmlinux.a
> >> --
> >>>> ld.lld: error: undefined symbol: efx_tc_netevent_event
> >> >>> referenced by ef100_netdev.c:329 (drivers/net/ethernet/sfc/ef100_netdev.c:329)
> >> >>> drivers/net/ethernet/sfc/ef100_netdev.o:(ef100_netevent_event) in archive vmlinux.a
> >
> > A cursory investigation leads me to thinking this occurs
> > if the CONFIG_SFC is set but CONFIG_SFC_SRIOV is not.
>
> Yep, looks that way. Patch on its way shortly.
Thanks Edward, much appreciated.
prev parent reply other threads:[~2023-06-13 5:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 13:10 [netdev-net-next:main 26/28] ld.lld: error: undefined symbol: efx_tc_netdev_event kernel test robot
2023-06-12 8:15 ` Simon Horman
2023-06-12 20:44 ` Edward Cree
2023-06-13 5:50 ` Simon Horman [this message]
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=ZIgDmJ9kgsfbZHm4@corigine.com \
--to=simon.horman@corigine.com \
--cc=ecree.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pieter.jansen-van-vuuren@amd.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 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.