From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2023-12-13 (ice, i40e)
Date: Fri, 15 Dec 2023 03:10:26 +0000 [thread overview]
Message-ID: <170260982662.2748.5524035806868477202.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231213220827.1311772-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net.git (main)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Wed, 13 Dec 2023 14:08:24 -0800 you wrote:
> This series contains updates to ice and i40e drivers.
>
> Michal Schmidt prevents possible out-of-bounds access for ice.
>
> Ivan Vecera corrects value for MDIO clause 45 on i40e.
>
> The following are changes since commit 810c38a369a0a0ce625b5c12169abce1dd9ccd53:
> net/rose: Fix Use-After-Free in rose_ioctl
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue 100GbE
>
> [...]
Here is the summary with links:
- [net,1/2] ice: fix theoretical out-of-bounds access in ethtool link modes
https://git.kernel.org/netdev/net/c/91f9181c7381
- [net,2/2] i40e: Fix ST code value for Clause 45
https://git.kernel.org/netdev/net/c/9b3daf2b0443
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-12-15 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 22:08 [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2023-12-13 (ice, i40e) Tony Nguyen
2023-12-13 22:08 ` [PATCH net 1/2] ice: fix theoretical out-of-bounds access in ethtool link modes Tony Nguyen
2023-12-13 22:08 ` [PATCH net 2/2] i40e: Fix ST code value for Clause 45 Tony Nguyen
2023-12-15 3:10 ` 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=170260982662.2748.5524035806868477202.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).