ntb: use correct mw_count function in ntb_tool and ntb_transport
authorLogan Gunthorpe <logang@deltatee.com>
Mon, 26 Jun 2017 19:50:41 +0000 (13:50 -0600)
committerJon Mason <jdmason@kudzu.us>
Mon, 17 Jul 2017 16:56:15 +0000 (12:56 -0400)
commitbc240eec4b074f5dc2753f295e980e66b72c90fb
treecffb7d4a2ac0b1b00f0ce483dad251c8ac9cd8c1
parent5771a8c08880cdca3bfb4a3fc6d309d6bba20877
ntb: use correct mw_count function in ntb_tool and ntb_transport

After converting to the new API, both ntb_tool and ntb_transport are
using ntb_mw_count to iterate through ntb_peer_get_addr when they
should be using ntb_peer_mw_count.

This probably isn't an issue with the Intel and AMD drivers but
this will matter for any future driver with asymetric memory window
counts.

Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
Acked-by: Allen Hubbe <Allen.Hubbe@emc.com>
Signed-off-by: Jon Mason <jdmason@kudzu.us>
Fixes: 443b9a14ecbe ("NTB: Alter MW API to support multi-ports devices")
drivers/ntb/ntb_transport.c
drivers/ntb/test/ntb_tool.c