From: patchwork-bot+netdevbpf@kernel.org
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, paulb@nvidia.com, eric.dumazet@gmail.com,
davem@davemloft.net, kuba@kernel.org, mika.penttila@nextfour.com,
ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
saeedm@nvidia.com, ozsh@nvidia.com, roid@nvidia.com,
vladbu@nvidia.com
Subject: Re: [PATCH net] skbuff: Fix build with SKB extensions disabled
Date: Thu, 08 Jul 2021 07:20:03 +0000 [thread overview]
Message-ID: <162572880314.15901.10011561624152819596.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210708041051.17851-1-f.fainelli@gmail.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 7 Jul 2021 21:10:51 -0700 you wrote:
> We will fail to build with CONFIG_SKB_EXTENSIONS disabled after
> 8550ff8d8c75 ("skbuff: Release nfct refcount on napi stolen or re-used
> skbs") since there is an unconditionally use of skb_ext_find() without
> an appropriate stub. Simply build the code conditionally and properly
> guard against both COFNIG_SKB_EXTENSIONS as well as
> CONFIG_NET_TC_SKB_EXT being disabled.
>
> [...]
Here is the summary with links:
- [net] skbuff: Fix build with SKB extensions disabled
https://git.kernel.org/netdev/net/c/9615fe36b31d
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:[~2021-07-08 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 4:10 [PATCH net] skbuff: Fix build with SKB extensions disabled Florian Fainelli
2021-07-08 6:24 ` Roi Dayan
2021-07-08 6:45 ` Eric Dumazet
2021-07-08 7: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=162572880314.15901.10011561624152819596.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=mika.penttila@nextfour.com \
--cc=netdev@vger.kernel.org \
--cc=ozsh@nvidia.com \
--cc=paulb@nvidia.com \
--cc=roid@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=vladbu@nvidia.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