netdev - Re: [net-next 01/15] net/mlx5: Add exit route when waiting for FW

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 11 May 2022 11:30:17 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Saeed Mahameed <saeedm@...dia.com>
Cc:     davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
        netdev@...r.kernel.org, gavinl@...dia.com, moshe@...dia.com
Subject: Re: [net-next 01/15] net/mlx5: Add exit route when waiting for FW

Hello:

This series was applied to netdev/net-next.git (master)
by Saeed Mahameed <saeedm@...dia.com>:

On Mon,  9 May 2022 22:57:29 -0700 you wrote:
> From: Gavin Li <gavinl@...dia.com>
> 
> Currently, removing a device needs to get the driver interface lock before
> doing any cleanup. If the driver is waiting in a loop for FW init, there
> is no way to cancel the wait, instead the device cleanup waits for the
> loop to conclude and release the lock.
> 
> [...]

Here is the summary with links:
  - [net-next,01/15] net/mlx5: Add exit route when waiting for FW
    https://git.kernel.org/netdev/net-next/c/8324a02c342a
  - [net-next,02/15] net/mlx5: Increase FW pre-init timeout for health recovery
    https://git.kernel.org/netdev/net-next/c/37ca95e62ee2
  - [net-next,03/15] net/mlx5: Lag, expose number of lag ports
    https://git.kernel.org/netdev/net-next/c/34a30d7635a8
  - [net-next,04/15] net/mlx5: devcom only supports 2 ports
    https://git.kernel.org/netdev/net-next/c/8a6e75e5f57e
  - [net-next,05/15] net/mlx5: Lag, move E-Switch prerequisite check into lag code
    https://git.kernel.org/netdev/net-next/c/4202ea95a6b6
  - [net-next,06/15] net/mlx5: Lag, use lag lock
    https://git.kernel.org/netdev/net-next/c/ec2fa47d7b98
  - [net-next,07/15] net/mlx5: Lag, filter non compatible devices
    https://git.kernel.org/netdev/net-next/c/bc4c2f2e0179
  - [net-next,08/15] net/mlx5: Lag, store number of ports inside lag object
    https://git.kernel.org/netdev/net-next/c/e9d5bb51c592
  - [net-next,09/15] net/mlx5: Lag, support single FDB only on 2 ports
    https://git.kernel.org/netdev/net-next/c/e2c45931ff12
  - [net-next,10/15] net/mlx5: Lag, use hash when in roce lag on 4 ports
    https://git.kernel.org/netdev/net-next/c/cdf611d17094
  - [net-next,11/15] net/mlx5: Lag, use actual number of lag ports
    https://git.kernel.org/netdev/net-next/c/7e978e7714d6
  - [net-next,12/15] net/mlx5: Support devices with more than 2 ports
    https://git.kernel.org/netdev/net-next/c/4cd14d44b11d
  - [net-next,13/15] net/mlx5: Lag, refactor dmesg print
    https://git.kernel.org/netdev/net-next/c/24b3599effe2
  - [net-next,14/15] net/mlx5: Lag, use buckets in hash mode
    https://git.kernel.org/netdev/net-next/c/352899f384d4
  - [net-next,15/15] net/mlx5: Lag, add debugfs to query hardware lag state
    https://git.kernel.org/netdev/net-next/c/7f46a0b7327a

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