From: Guoqing Jiang <jgq516@gmail.com>
To: dledford@redhat.com, jgg@ziepe.ca, corbet@lwn.net
Cc: linux-rdma@vger.kernel.org, linux-doc@vger.kernel.org,
Guoqing Jiang <guoqing.jiang@cloud.ionos.com>,
Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Subject: [PATCH] Documentation/infiniband: update name of some functions
Date: Tue, 3 Sep 2019 14:45:19 +0200 [thread overview]
Message-ID: <20190903124519.28318-1-guoqing.jiang@cloud.ionos.com> (raw)
Update the document since those functions had been renamed in below.
commit 0a18cfe4f6d7d ("IB/core: Rename ib_create_ah to rdma_create_ah")
commit 67b985b6c7553 ("IB/core: Rename ib_modify_ah to rdma_modify_ah")
commit bfbfd661c9ea2 ("IB/core: Rename ib_query_ah to rdma_query_ah")
commit 365231593409f ("IB/core: Rename ib_destroy_ah to rdma_destroy_ah")
Cc: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Signed-off-by: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
---
Documentation/infiniband/core_locking.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/infiniband/core_locking.rst b/Documentation/infiniband/core_locking.rst
index f34669beb4fe..8f76a8a5a38f 100644
--- a/Documentation/infiniband/core_locking.rst
+++ b/Documentation/infiniband/core_locking.rst
@@ -29,10 +29,10 @@ Sleeping and interrupt context
The corresponding functions exported to upper level protocol
consumers:
- - ib_create_ah
- - ib_modify_ah
- - ib_query_ah
- - ib_destroy_ah
+ - rdma_create_ah
+ - rdma_modify_ah
+ - rdma_query_ah
+ - rdma_destroy_ah
- ib_post_send
- ib_post_recv
- ib_req_notify_cq
--
2.17.1
next reply other threads:[~2019-09-03 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 12:45 Guoqing Jiang [this message]
2019-09-12 13:27 ` [PATCH] Documentation/infiniband: update name of some functions Jason Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190903124519.28318-1-guoqing.jiang@cloud.ionos.com \
--to=jgq516@gmail.com \
--cc=corbet@lwn.net \
--cc=dledford@redhat.com \
--cc=guoqing.jiang@cloud.ionos.com \
--cc=jgg@ziepe.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=niranjana.vishwanathapura@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).