diff options
author | Leon Romanovsky <leonro@nvidia.com> | 2021-08-01 11:37:57 +0300 |
---|---|---|
committer | Saeed Mahameed <saeedm@nvidia.com> | 2021-08-11 11:14:30 -0700 |
commit | 8e792700b994a4b79abe1303eb379bbd1f4212be (patch) | |
tree | ea627c98841f8b57d9bdaaf7bb4ded75fc308655 /drivers/nvmem | |
parent | 90b85d4e313caa73251f5da18786fd1909ff66bc (diff) | |
download | linux-8e792700b994a4b79abe1303eb379bbd1f4212be.tar.gz linux-8e792700b994a4b79abe1303eb379bbd1f4212be.tar.bz2 linux-8e792700b994a4b79abe1303eb379bbd1f4212be.zip |
net/mlx5: Delete impossible dev->state checks
New mlx5_core device structure is allocated through devlink_alloc
with\ kzalloc and that ensures that all fields are equal to zero
and it includes ->state too.
That means that checks of that field in the mlx5_init_one() is
completely redundant, because that function is called only once
in the begging of mlx5_core_dev lifetime.
PCI:
.probe()
-> probe_one()
-> mlx5_init_one()
The recovery flow can't run at that time or before it, because relevant
work initialized later in mlx5_init_once().
Such initialization flow ensures that dev->state can't be
MLX5_DEVICE_STATE_UNINITIALIZED at all, so remove such impossible
checks.
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'drivers/nvmem')
0 files changed, 0 insertions, 0 deletions