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-07-21 (i40e, iavf)
Date: Tue, 25 Jul 2023 00:20:20 +0000 [thread overview]
Message-ID: <169024442097.15014.3686941471612516296.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230721155812.1292752-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 Fri, 21 Jul 2023 08:58:09 -0700 you wrote:
> This series contains updates to i40e and iavf drivers.
>
> Wang Ming corrects an error check on i40e.
>
> Jake unlocks crit_lock on allocation failure to prevent deadlock and
> stops re-enabling of interrupts when it's not intended for iavf.
>
> [...]
Here is the summary with links:
- [net,1/3] i40e: Fix an NULL vs IS_ERR() bug for debugfs_create_dir()
https://git.kernel.org/netdev/net/c/043b1f185fb0
- [net,2/3] iavf: fix potential deadlock on allocation failure
https://git.kernel.org/netdev/net/c/a2f054c10bef
- [net,3/3] iavf: check for removal state before IAVF_FLAG_PF_COMMS_FAILED
https://git.kernel.org/netdev/net/c/91896c8acce2
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-07-25 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 15:58 [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2023-07-21 (i40e, iavf) Tony Nguyen
2023-07-21 15:58 ` [PATCH net 1/3] i40e: Fix an NULL vs IS_ERR() bug for debugfs_create_dir() Tony Nguyen
2023-07-21 15:58 ` [PATCH net 2/3] iavf: fix potential deadlock on allocation failure Tony Nguyen
2023-07-21 15:58 ` [PATCH net 3/3] iavf: check for removal state before IAVF_FLAG_PF_COMMS_FAILED Tony Nguyen
2023-07-25 0: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=169024442097.15014.3686941471612516296.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).