diff options
| author | Jiri Pirko <jiri@nvidia.com> | 2023-06-06 00:12:17 -0700 |
|---|---|---|
| committer | Saeed Mahameed <saeedm@nvidia.com> | 2023-06-07 14:00:44 -0700 |
| commit | 97bd788efb9052963b43ba41c8aaff3ed12e1ede (patch) | |
| tree | 9edd9522e133a67a62358425b150e0e84682157a /net/ipv4/tcp_output.c | |
| parent | de1f0a650824ed1905d5d48190f65f309cee5163 (diff) | |
| download | linux-97bd788efb9052963b43ba41c8aaff3ed12e1ede.tar.gz linux-97bd788efb9052963b43ba41c8aaff3ed12e1ede.tar.bz2 linux-97bd788efb9052963b43ba41c8aaff3ed12e1ede.zip | |
net/mlx5: Skip inline mode check after mlx5_eswitch_enable_locked() failure
Commit bffaa916588e ("net/mlx5: E-Switch, Add control for inline mode")
added inline mode checking to esw_offloads_start() with a warning
printed out in case there is a problem. Tne inline mode checking was
done even after mlx5_eswitch_enable_locked() call failed, which is
pointless.
Later on, commit 8c98ee77d911 ("net/mlx5e: E-Switch, Add extack messages
to devlink callbacks") converted the error/warning prints to extack
setting, which caused that the inline mode check error to overwrite
possible previous extack message when mlx5_eswitch_enable_locked()
failed. User then gets confusing error message.
Fix this by skipping check of inline mode after
mlx5_eswitch_enable_locked() call failed.
Signed-off-by: Jiri Pirko <jiri@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'net/ipv4/tcp_output.c')
0 files changed, 0 insertions, 0 deletions