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/3][pull request] Intel Wired LAN Driver Updates 2023-03-21 (ice)
Date: Thu, 23 Mar 2023 05:50:18 +0000 [thread overview]
Message-ID: <167955061868.14332.2482366315808559060.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230321183641.2849726-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 Tue, 21 Mar 2023 11:36:38 -0700 you wrote:
> This series contains updates to ice driver only.
>
> Piotr sets first_desc field for proper handling of Flow Director
> packets.
>
> Michal moves error checking for VF earlier in function to properly return
> error before other checks/reporting; he also corrects VSI filter removal to
> be done during VSI removal and not rebuild.
>
> [...]
Here is the summary with links:
- [net,1/3] ice: fix rx buffers handling for flow director packets
https://git.kernel.org/netdev/net/c/387d42ae6df7
- [net,2/3] ice: check if VF exists before mode check
https://git.kernel.org/netdev/net/c/83b49e7f63da
- [net,3/3] ice: remove filters only if VSI is deleted
https://git.kernel.org/netdev/net/c/7d46c0e670d5
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-03-23 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 18:36 [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2023-03-21 (ice) Tony Nguyen
2023-03-21 18:36 ` [PATCH net 1/3] ice: fix rx buffers handling for flow director packets Tony Nguyen
2023-03-21 18:36 ` [PATCH net 2/3] ice: check if VF exists before mode check Tony Nguyen
2023-03-21 18:36 ` [PATCH net 3/3] ice: remove filters only if VSI is deleted Tony Nguyen
2023-03-23 5:50 ` 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=167955061868.14332.2482366315808559060.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.