From: patchwork-bot+netdevbpf@kernel.org
To: <edward.cree@amd.com>
Cc: linux-net-drivers@amd.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, ecree.xilinx@gmail.com,
netdev@vger.kernel.org, habetsm.xilinx@gmail.com,
oe-kbuild-all@lists.linux.dev, simon.horman@corigine.com,
pieter.jansen-van-vuuren@amd.com, naresh.kamboju@linaro.org,
lkp@intel.com
Subject: Re: [PATCH v2 net-next] sfc: do not try to call tc functions when CONFIG_SFC_SRIOV=n
Date: Fri, 16 Jun 2023 08:20:19 +0000 [thread overview]
Message-ID: <168690361978.13714.16133018806153868167.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230615215243.34942-1-edward.cree@amd.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 15 Jun 2023 22:52:43 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> Functions efx_tc_netdev_event and efx_tc_netevent_event do not exist
> in that case as object files tc_bindings.o and tc_encap_actions.o
> are not built, so the calls to them from ef100_netdev_event and
> ef100_netevent_event cause link errors.
> Wrap the corresponding header files (tc_bindings.h, tc_encap_actions.h)
> with #if IS_ENABLED(CONFIG_SFC_SRIOV), and add an #else with static
> inline stubs for these two functions.
>
> [...]
Here is the summary with links:
- [v2,net-next] sfc: do not try to call tc functions when CONFIG_SFC_SRIOV=n
https://git.kernel.org/netdev/net-next/c/c08afcdcf952
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-06-16 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 21:52 [PATCH v2 net-next] sfc: do not try to call tc functions when CONFIG_SFC_SRIOV=n edward.cree
2023-06-16 7:44 ` Martin Habets
2023-06-16 8:20 ` patchwork-bot+netdevbpf [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=168690361978.13714.16133018806153868167.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=lkp@intel.com \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).