From: Edward Cree <ecree.xilinx@gmail•com>
To: Naresh Kamboju <naresh.kamboju@linaro•org>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
open list <linux-kernel@vger•kernel.org>,
Netdev <netdev@vger•kernel.org>,
lkft-triage@lists•linaro.org
Cc: Arnd Bergmann <arnd@arndb•de>,
"David S. Miller" <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>,
Anders Roxell <anders.roxell@linaro•org>,
habetsm.xilinx@gmail•com
Subject: Re: powerpc: ERROR: modpost: "efx_tc_netevent_event" [drivers/net/ethernet/sfc/sfc.ko] undefined!
Date: Thu, 15 Jun 2023 22:21:15 +0100 [thread overview]
Message-ID: <07503ee4-591c-17ba-6e56-91e5b3047c16@gmail.com> (raw)
In-Reply-To: <CA+G9fYsAvbqVr+W4=17sxwguGSQi6cU+9WZ_YQzg3Wj96e70uQ@mail.gmail.com>
On 15/06/2023 14:57, Naresh Kamboju wrote:
> Following build regressions noticed on Linux next-20230615.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro•org>
>
> Regressions found on powerpc:
>
> - build/gcc-8-ppc6xx_defconfig
> - build/gcc-12-ppc6xx_defconfig
>
>
> buid log:
> ====
> ERROR: modpost: "efx_tc_netevent_event"
> [drivers/net/ethernet/sfc/sfc.ko] undefined!
> ERROR: modpost: "efx_tc_netdev_event"
> [drivers/net/ethernet/sfc/sfc.ko] undefined!
> make[2]: *** [/builds/linux/scripts/Makefile.modpost:137:
> Module.symvers] Error 1
Known issue with CONFIG_SFC=[ym] and CONFIG_SFC_SRIOV=n.
Fix already under way; v1 [1] had changes requested, v2 coming soon.
But thank you for testing. I'll cc you on v2 in case you want to test the fix.
-ed
[1]: https://lore.kernel.org/all/20230612205428.1780-1-edward.cree@amd.com/
prev parent reply other threads:[~2023-06-15 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 13:57 powerpc: ERROR: modpost: "efx_tc_netevent_event" [drivers/net/ethernet/sfc/sfc.ko] undefined! Naresh Kamboju
2023-06-15 21:21 ` Edward Cree [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=07503ee4-591c-17ba-6e56-91e5b3047c16@gmail.com \
--to=ecree.xilinx@gmail$(echo .)com \
--cc=anders.roxell@linaro$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=davem@davemloft$(echo .)net \
--cc=habetsm.xilinx@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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