public inbox for netdev@vger.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, netdev@vger•kernel.org,
	sassmann@redhat•com
Subject: Re: [PATCH net 0/8][pull request] Intel Wired LAN Driver Updates 2022-02-25
Date: Sat, 26 Feb 2022 13:00:11 +0000	[thread overview]
Message-ID: <164588041146.8718.9913656272536439293.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220225194614.136571-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 Fri, 25 Feb 2022 11:46:06 -0800 you wrote:
> This series contains updates to iavf driver only.
> 
> Slawomir fixes stability issues that can be seen when stressing the
> driver using a large number of VFs with a multitude of operations.
> Among the fixes are reworking mutexes to provide more effective locking,
> ensuring initialization is complete before teardown, preventing
> operations which could race while removing the driver, stopping certain
> tasks from being queued when the device is down, and adding a missing
> mutex unlock.
> 
> [...]

Here is the summary with links:
  - [net,1/8] iavf: Rework mutexes for better synchronisation
    https://git.kernel.org/netdev/net/c/fc2e6b3b132a
  - [net,2/8] iavf: Add waiting so the port is initialized in remove
    https://git.kernel.org/netdev/net/c/974578017fc1
  - [net,3/8] iavf: Fix init state closure on remove
    https://git.kernel.org/netdev/net/c/3ccd54ef44eb
  - [net,4/8] iavf: Fix locking for VIRTCHNL_OP_GET_OFFLOAD_VLAN_V2_CAPS
    https://git.kernel.org/netdev/net/c/0579fafd37fb
  - [net,5/8] iavf: Fix race in init state
    https://git.kernel.org/netdev/net/c/a472eb5cbaeb
  - [net,6/8] iavf: Fix deadlock in iavf_reset_task
    https://git.kernel.org/netdev/net/c/e85ff9c631e1
  - [net,7/8] iavf: Fix missing check for running netdev
    https://git.kernel.org/netdev/net/c/d2c0f45fcceb
  - [net,8/8] iavf: Fix __IAVF_RESETTING state usage
    https://git.kernel.org/netdev/net/c/14756b2ae265

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



      parent reply	other threads:[~2022-02-26 13:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 19:46 [PATCH net 0/8][pull request] Intel Wired LAN Driver Updates 2022-02-25 Tony Nguyen
2022-02-25 19:46 ` [PATCH net 1/8] iavf: Rework mutexes for better synchronisation Tony Nguyen
2022-02-25 19:46 ` [PATCH net 2/8] iavf: Add waiting so the port is initialized in remove Tony Nguyen
2022-02-25 19:46 ` [PATCH net 3/8] iavf: Fix init state closure on remove Tony Nguyen
2022-02-25 19:46 ` [PATCH net 4/8] iavf: Fix locking for VIRTCHNL_OP_GET_OFFLOAD_VLAN_V2_CAPS Tony Nguyen
2022-02-25 19:46 ` [PATCH net 5/8] iavf: Fix race in init state Tony Nguyen
2022-02-25 19:46 ` [PATCH net 6/8] iavf: Fix deadlock in iavf_reset_task Tony Nguyen
2022-02-25 19:46 ` [PATCH net 7/8] iavf: Fix missing check for running netdev Tony Nguyen
2022-02-25 19:46 ` [PATCH net 8/8] iavf: Fix __IAVF_RESETTING state usage Tony Nguyen
2022-02-26 13:00 ` 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=164588041146.8718.9913656272536439293.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=anthony.l.nguyen@intel$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=sassmann@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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