From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
maciej.fijalkowski@intel.com, magnus.karlsson@intel.com,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, bpf@vger.kernel.org
Subject: Re: [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2021-11-22
Date: Tue, 23 Nov 2021 12:20:10 +0000 [thread overview]
Message-ID: <163767001014.10565.1715922992675329504.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211122184522.147331-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net.git (master)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Mon, 22 Nov 2021 10:45:20 -0800 you wrote:
> Maciej Fijalkowski says:
>
> Here are the two fixes for issues around ethtool's set_channels()
> callback for ice driver. Both are related to XDP resources. First one
> corrects the size of vsi->txq_map that is used to track the usage of Tx
> resources and the second one prevents the wrong refcounting of bpf_prog.
>
> [...]
Here is the summary with links:
- [net,1/2] ice: fix vsi->txq_map sizing
https://git.kernel.org/netdev/net/c/792b2086584f
- [net,2/2] ice: avoid bpf_prog refcount underflow
https://git.kernel.org/netdev/net/c/f65ee535df77
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-11-23 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 18:45 [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2021-11-22 Tony Nguyen
2021-11-22 18:45 ` [PATCH net 1/2] ice: fix vsi->txq_map sizing Tony Nguyen
2021-11-22 18:45 ` [PATCH net 2/2] ice: avoid bpf_prog refcount underflow Tony Nguyen
2021-11-23 12: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=163767001014.10565.1715922992675329504.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.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 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).