net/mlx5: Separate probe vs. reload flows
authorLeon Romanovsky <leonro@nvidia.com>
Mon, 2 Nov 2020 14:54:43 +0000 (16:54 +0200)
committerSaeed Mahameed <saeedm@nvidia.com>
Thu, 11 Mar 2021 22:35:10 +0000 (14:35 -0800)
commit6dea2f7eff9659049f90922283756830364e6278
tree85a95ee5c599ad359f4f208181045d94b559a0d0
parentd89edb36070572e1b8889009fc3c143e7c290e16
net/mlx5: Separate probe vs. reload flows

The mix between probe/unprobe and reload flows causes to have an extra
mutex lock intf_state_mutex that generates LOCKDEP warning between it
and devlink_mutex. As a preparation for the future removal, separate
those flows.

Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
drivers/net/ethernet/mellanox/mlx5/core/devlink.c
drivers/net/ethernet/mellanox/mlx5/core/fw_reset.c
drivers/net/ethernet/mellanox/mlx5/core/main.c
drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.h
drivers/net/ethernet/mellanox/mlx5/core/sf/dev/driver.c