UCP/CORE/WIREUP: Fix review comments

kunpengcompute · Dec 3, 2020 · fd5d2e8 · fd5d2e8
1 parent 87f54ea
commit fd5d2e8
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/src/ucp/core/ucp_ep.c b/src/ucp/core/ucp_ep.c
@@ -1036,7 +1036,7 @@ ucs_status_ptr_t ucp_ep_close_nbx(ucp_ep_h ep, const ucp_request_param_t *param)
          * was forcibly closed from a user's error handling callback after
          * disconnect event was received, but some EP flush operation still
          * is in-progress, so, the destroyed EP will be touched upon flush
-         * completion om some transport */
+         * completion on some transport */
         if (!(ep->flags & UCP_EP_FLAG_FAILED)) {
             ucp_ep_discard_lanes(ep, UCS_ERR_CANCELED);
         }

diff --git a/src/ucp/wireup/wireup.c b/src/ucp/wireup/wireup.c
@@ -339,11 +339,11 @@ void ucp_wireup_remote_connected(ucp_ep_h ep)
     ucs_trace("ep %p: remote connected", ep);
     if (!(ep->flags & UCP_EP_FLAG_CLOSED)) {
         /* set REMOTE_CONNECTED flag if an EP is not closed, otherwise -
-         * just make UCT EPs are remote connected to remove WIREUP_EP
-         * for them and complete flush(LOCAL) operation in UCP EP close
-         * procedure (don't set REMOTE_CONNECTED flag to avoid possible
-         * wrong behavior in ucp_ep_close_flushed_callback() when a peer was
-         * already disconnected, but we set REMOTE_CONNECTED flag again) */
+         * just make UCT EPs remote connected to remove WIREUP_EP for them
+         * and complete flush(LOCAL) operation in UCP EP close procedure
+         * (don't set REMOTE_CONNECTED flag to avoid possible wrong behavior
+         * in ucp_ep_close_flushed_callback() when a peer was already
+         * disconnected, but we set REMOTE_CONNECTED flag again) */
         ep->flags |= UCP_EP_FLAG_REMOTE_CONNECTED;
     }