From: Yajun Deng <yajun.deng@linux.dev>
To: jgg@nvidia.com, selvin.xavier@broadcom.com, galpress@amazon.com,
sleybo@amazon.com, liangwenpeng@huawei.com, liweihang@huawei.com,
mustafa.ismail@intel.com, shiraz.saleem@intel.com,
leonro@nvidia.com, dennis.dalessandro@cornelisnetworks.com,
mike.marciniszyn@cornelisnetworks.com, zyjzyj2000@gmail.com
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
Yajun Deng <yajun.deng@linux.dev>
Subject: [PATCH for-next 0/9] RDMA: get rid of create_user_ah
Date: Tue, 8 Mar 2022 22:34:28 +0800 [thread overview]
Message-ID: <20220308143428.3401170-1-yajun.deng@linux.dev> (raw)
The two members create_user_ah and create_ah in struct ib_device_ops
are very similar. we can use create_ah for all case. so get rid of
create_user_ah.
Yajun Deng (9):
RDMA/core: get rid of create_user_ah
RDMA/bnxt_re: get rid of create_user_ah
RDMA/efa: get rid of create_user_ah
RDMA/hns: get rid of create_user_ah
RDMA/irdma: get rid of create_user_ah
RDMA/mlx5: get rid of create_user_ah
RDMA/ocrdma: get rid of create_user_ah
RDMA/rdmavt: get rid of create_user_ah
RDMA/rxe: get rid of create_user_ah
drivers/infiniband/core/device.c | 1 -
drivers/infiniband/core/uverbs_cmd.c | 2 +-
drivers/infiniband/core/verbs.c | 7 ++-----
drivers/infiniband/hw/bnxt_re/main.c | 1 -
drivers/infiniband/hw/efa/efa_main.c | 2 +-
drivers/infiniband/hw/efa/efa_verbs.c | 5 +++++
drivers/infiniband/hw/hns/hns_roce_main.c | 1 -
drivers/infiniband/hw/irdma/verbs.c | 1 -
drivers/infiniband/hw/mlx5/main.c | 1 -
drivers/infiniband/hw/ocrdma/ocrdma_main.c | 1 -
drivers/infiniband/sw/rdmavt/vt.c | 1 -
drivers/infiniband/sw/rxe/rxe_verbs.c | 1 -
include/rdma/ib_verbs.h | 2 --
13 files changed, 9 insertions(+), 17 deletions(-)
--
2.25.1
next reply other threads:[~2022-03-08 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 14:34 Yajun Deng [this message]
2022-03-09 9:21 ` [PATCH for-next 0/9] RDMA: get rid of create_user_ah Leon Romanovsky
2022-03-09 9:34 ` Yajun Deng
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=20220308143428.3401170-1-yajun.deng@linux.dev \
--to=yajun.deng@linux.dev \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=galpress@amazon.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=liangwenpeng@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=liweihang@huawei.com \
--cc=mike.marciniszyn@cornelisnetworks.com \
--cc=mustafa.ismail@intel.com \
--cc=selvin.xavier@broadcom.com \
--cc=shiraz.saleem@intel.com \
--cc=sleybo@amazon.com \
--cc=zyjzyj2000@gmail.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