public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yanjun Zhu <yanjun.zhu@linux.dev>
To: Yajun Deng <yajun.deng@linux.dev>,
	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
Subject: Re: [PATCH for-next 9/9] RDMA/rxe: get rid of create_user_ah
Date: Wed, 9 Mar 2022 21:43:05 +0800	[thread overview]
Message-ID: <f6da67eb-4f18-d1f1-6ec4-c9f927723421@linux.dev> (raw)
In-Reply-To: <20220308144033.3406606-1-yajun.deng@linux.dev>

在 2022/3/8 22:40, Yajun Deng 写道:
> There is no create_user_ah in ib_device_ops, remove it.
In the file include/rdma/ib_verbs.h:

2305 struct ib_device_ops {
...
2431         int (*create_user_ah)(struct ib_ah *ah, struct 
rdma_ah_init_attr *attr,
2432                               struct ib_udata *udata);
...

create_user_ah exists.

Zhu Yanjun
> 
> Signed-off-by: Yajun Deng <yajun.deng@linux.dev>
> ---
>   drivers/infiniband/sw/rxe/rxe_verbs.c | 1 -
>   1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.c b/drivers/infiniband/sw/rxe/rxe_verbs.c
> index 80df9a8f71a1..fa0cf2554425 100644
> --- a/drivers/infiniband/sw/rxe/rxe_verbs.c
> +++ b/drivers/infiniband/sw/rxe/rxe_verbs.c
> @@ -1053,7 +1053,6 @@ static const struct ib_device_ops rxe_dev_ops = {
>   	.create_cq = rxe_create_cq,
>   	.create_qp = rxe_create_qp,
>   	.create_srq = rxe_create_srq,
> -	.create_user_ah = rxe_create_ah,
>   	.dealloc_driver = rxe_dealloc,
>   	.dealloc_mw = rxe_dealloc_mw,
>   	.dealloc_pd = rxe_dealloc_pd,


  reply	other threads:[~2022-03-09 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 14:40 [PATCH for-next 9/9] RDMA/rxe: get rid of create_user_ah Yajun Deng
2022-03-09 13:43 ` Yanjun Zhu [this message]
2022-03-09 13:48   ` Yanjun Zhu

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=f6da67eb-4f18-d1f1-6ec4-c9f927723421@linux.dev \
    --to=yanjun.zhu@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=yajun.deng@linux.dev \
    --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