Commit graph

6 commits

Author SHA1 Message Date
DataHoarder d701c1f0c7 fm10k: convert to new udp_tunnel_nic infra (support kernel >= 5.12.0)
Some checks reported errors
continuous-integration/drone/push Build was killed
continuous-integration/drone/pr Build was killed
Straightforward conversion to new infra. Driver restores info
after close/open cycle by calling its internal restore function
so just use that, no need for udp_tunnel_nic_reset_ntf() here.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

Based off linux commit f7529b4ba3c98470b0e367ba447ad0da84dc308c
2021-08-04 04:16:43 +02:00
Christophe JAILLET 279ad02edf fm10k: Fix an error handling path in 'fm10k_probe()'
If an error occurs after a 'pci_enable_pcie_error_reporting()' call, it
must be undone by a corresponding 'pci_disable_pcie_error_reporting()'
call, as already done in the remove function.

Fixes: 19ae1b3fb99c ("fm10k: Add support for PCI power management and error handling")
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
2021-08-04 03:58:20 +02:00
Jesse Brandeburg 9221eea3b0 fm10k: move error check
The error check and set_bit are placed in such a way that sparse (C=2)
warns:
.../fm10k_pci.c:1395:9: warning: context imbalance in 'fm10k_msix_mbx_pf' - different lock contexts for basic block

Which seems a little odd, but the code can obviously be moved
to where the variable is being set without changing functionality
at all, and it even seems to make a bit more sense with the check
closer to the set.

Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
2021-08-04 03:57:36 +02:00
DataHoarder 118e827b0e Intel release 0.27.1 2020-10-20 20:13:24 +02:00
Silicom Ltd 7cf35a4864 Intel release 0.26.1 2020-10-20 20:06:27 +02:00
Silicom Ltd 1e989c9e83 Intel release 0.20.1 2020-10-20 20:05:04 +02:00