All of lore.kernel.org
 help / color / mirror / Atom feed
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-03-21 (iavf, i40e)
Date: Thu, 23 Mar 2023 05:50:18 +0000	[thread overview]
Message-ID: <167955061863.14332.18264684431925581838.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230321183548.2849671-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:35:46 -0700 you wrote:
> This series contains updates to iavf and i40e drivers.
> 
> Stefan Assmann adds check, and return, if driver has already gone
> through remove to prevent hang for iavf.
> 
> Radoslaw adds zero initialization to ensure Flow Director packets are
> populated with correct values for i40e.
> 
> [...]

Here is the summary with links:
  - [net,1/2] iavf: fix hang on reboot with ice
    https://git.kernel.org/netdev/net/c/4e264be98b88
  - [net,2/2] i40e: fix flow director packet filter programming
    https://git.kernel.org/netdev/net/c/c672297bbc0e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-03-23  5:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 18:35 [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2023-03-21 (iavf, i40e) Tony Nguyen
2023-03-21 18:35 ` [PATCH net 1/2] iavf: fix hang on reboot with ice Tony Nguyen
2023-03-21 18:35 ` [PATCH net 2/2] i40e: fix flow director packet filter programming 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=167955061863.14332.18264684431925581838.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.