From: Edward Cree <ecree@amd.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH net-next 04/14] sfc: determine wire m-port at EF100 PF probe time
Date: Tue, 26 Jul 2022 15:21:42 +0100 [thread overview]
Message-ID: <71210e55-5484-dc86-fb46-88fbacd8a083@amd.com> (raw)
In-Reply-To: <202207231215.nHYCJokG-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
On 23/07/2022 05:15, kernel test robot wrote:
> All errors (new ones prefixed by >>):
>
> s390-linux-ld: s390-linux-ld: DWARF error: could not find abbrev number 5931
> drivers/net/ethernet/sfc/ef100_nic.o: in function `ef100_probe_netdev_pf':
> ef100_nic.c:(.text+0x2520): undefined reference to `efx_mae_mport_wire'
>>> s390-linux-ld: ef100_nic.c:(.text+0x2534): undefined reference to `efx_mae_lookup_mport'
Oh, I see what's wrong here.
mae.o is under CONFIG_SFC_SRIOV in the Makefile, but these calls into it
are made unconditionally. And I hadn't thought to test with
CONFIG_SFC_SRIOV=n. (D'oh!)
I'm able to reproduce on x86_64 with that config change, will fix in v2.
-ed
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 1181 bytes --]
next prev parent reply other threads:[~2022-07-26 14:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 16:04 [PATCH net-next 00/14] sfc: VF representors for EF100 - RX side ecree
2022-07-22 16:04 ` [PATCH net-next 01/14] sfc: plumb ef100 representor stats ecree
2022-07-22 16:04 ` [PATCH net-next 02/14] sfc: ef100 representor RX NAPI poll ecree
2022-07-22 16:04 ` [PATCH net-next 03/14] sfc: ef100 representor RX top half ecree
2022-07-22 16:04 ` [PATCH net-next 04/14] sfc: determine wire m-port at EF100 PF probe time ecree
2022-07-23 3:04 ` kernel test robot
2022-07-23 4:15 ` kernel test robot
2022-07-26 14:21 ` Edward Cree [this message]
2022-07-22 16:04 ` [PATCH net-next 05/14] sfc: check ef100 RX packets are from the wire ecree
2022-07-22 16:04 ` [PATCH net-next 06/14] sfc: receive packets from EF100 VFs into representors ecree
2022-07-23 7:18 ` kernel test robot
2022-07-22 16:04 ` [PATCH net-next 07/14] sfc: insert default MAE rules to connect VFs to representors ecree
2022-07-22 16:04 ` [PATCH net-next 08/14] sfc: move table locking into filter_table_{probe,remove} methods ecree
2022-07-22 16:04 ` [PATCH net-next 09/14] sfc: use a dynamic m-port for representor RX and set it promisc ecree
2022-07-22 16:04 ` [PATCH net-next 10/14] sfc: look up VF's client ID when creating representor ecree
2022-07-22 16:04 ` [PATCH net-next 11/14] sfc: fetch existing assigned MAC address from FW when creating VF rep ecree
2022-07-22 16:04 ` [PATCH net-next 12/14] sfc: set EF100 VF MAC address through representor ecree
2022-07-22 16:04 ` [PATCH net-next 13/14] sfc: get provisioned MAC address on EF100 VF probe ecree
2022-07-22 16:04 ` [PATCH net-next 14/14] sfc: implement ethtool get/set RX ring size for EF100 reps ecree
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=71210e55-5484-dc86-fb46-88fbacd8a083@amd.com \
--to=ecree@amd.com \
--cc=kbuild-all@lists.01.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 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.