diff options
| author | Logan Gunthorpe <logang@deltatee.com> | 2017-06-26 13:50:41 -0600 |
|---|---|---|
| committer | Jon Mason <jdmason@kudzu.us> | 2017-07-17 12:56:15 -0400 |
| commit | bc240eec4b074f5dc2753f295e980e66b72c90fb (patch) | |
| tree | cffb7d4a2ac0b1b00f0ce483dad251c8ac9cd8c1 /drivers/ntb/test | |
| parent | 5771a8c08880cdca3bfb4a3fc6d309d6bba20877 (diff) | |
| download | linux-bc240eec4b074f5dc2753f295e980e66b72c90fb.tar.gz linux-bc240eec4b074f5dc2753f295e980e66b72c90fb.tar.bz2 linux-bc240eec4b074f5dc2753f295e980e66b72c90fb.zip | |
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")
Diffstat (limited to 'drivers/ntb/test')
| -rw-r--r-- | drivers/ntb/test/ntb_tool.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/ntb/test/ntb_tool.c b/drivers/ntb/test/ntb_tool.c index f002bf48a08d..a69815c45ce6 100644 --- a/drivers/ntb/test/ntb_tool.c +++ b/drivers/ntb/test/ntb_tool.c @@ -959,7 +959,7 @@ static int tool_probe(struct ntb_client *self, struct ntb_dev *ntb) tc->ntb = ntb; init_waitqueue_head(&tc->link_wq); - tc->mw_count = min(ntb_mw_count(tc->ntb, PIDX), MAX_MWS); + tc->mw_count = min(ntb_peer_mw_count(tc->ntb), MAX_MWS); for (i = 0; i < tc->mw_count; i++) { rc = tool_init_mw(tc, i); if (rc) |