Dave Jiang f3fd2afed8 ntb: transport shouldn't disable link due to bogus values in SPADs ... It seems that under certain scenarios the SPAD can have bogus values caused by an agent (i.e. BIOS or other software) that is not the kernel driver, and that causes memory window setup failure. This should not cause the link to be disabled because if we do that, the driver will never recover again. We have verified in testing that this issue happens and prevents proper link recovery. Signed-off-by: Dave Jiang <dave.jiang@intel.com> Acked-by: Allen Hubbe <Allen.Hubbe@dell.com> Signed-off-by: Jon Mason <jdmason@kudzu.us> Fixes: 84f766855f ("ntb: stop link work when we do not have memory")		2017-08-01 13:31:44 -04:00
..
hw	NTB: Add IDT 89HPESxNTx PCIe-switches support	2017-07-06 11:30:07 -04:00
test	ntb: use correct mw_count function in ntb_tool and ntb_transport	2017-07-17 12:56:15 -04:00
Kconfig	NTB: Add ping pong test client	2015-07-04 14:07:42 -04:00
Makefile	NTB: Add ping pong test client	2015-07-04 14:07:42 -04:00
ntb.c	NTB: Add Messaging NTB API	2017-07-06 11:30:07 -04:00
ntb_transport.c	ntb: transport shouldn't disable link due to bogus values in SPADs	2017-08-01 13:31:44 -04:00