From b60804ffa253b534701529236a8a41e7920edfa4 Mon Sep 17 00:00:00 2001 From: Alexia Ingerson Date: Mon, 21 Aug 2023 10:10:21 -0700 Subject: [PATCH] man/fi_peer: fix fi_peer man page inconsistency The function names are get_msg and get_tag, not get_msg_entry and get_tag_entry Signed-off-by: Alexia Ingerson --- man/fi_peer.3.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/man/fi_peer.3.md b/man/fi_peer.3.md index bf84ba28d56..45bbac0a2bf 100644 --- a/man/fi_peer.3.md +++ b/man/fi_peer.3.md @@ -488,7 +488,7 @@ peer can initialize any extra available data before queuing the message with the owner. The peer_context and owner_context fields are only modifiable by the peer and owner, respectively, to store extra provider-specific information. -## fi_ops_srx_owner::get_msg_entry() / get_tag_entry() +## fi_ops_srx_owner::get_msg() / get_tag() These calls are invoked by the peer provider to obtain the receive buffer(s) where an incoming message should be placed. The peer provider will pass in @@ -533,7 +533,7 @@ entry. ## fi_ops_srx_peer::start_msg() / start_tag() -These calls indicate that an asynchronous get_msg_entry() or get_tag_entry() +These calls indicate that an asynchronous get_msg() or get_tag() has completed and a buffer is now available to receive the message. Control of the fi_peer_rx_entry is returned to the peer provider and has been initialized for receiving the incoming message.