public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Leon Romanovsky" <leonro@nvidia.com>
Cc: 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,
	dennis.dalessandro@cornelisnetworks.com,
	mike.marciniszyn@cornelisnetworks.com, zyjzyj2000@gmail.com,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-next 0/9] RDMA: get rid of create_user_ah
Date: Wed, 09 Mar 2022 09:34:47 +0000	[thread overview]
Message-ID: <9e6973cfbca0ef70bfd57f499a7f5397@linux.dev> (raw)
In-Reply-To: <Yihxh3HdEqu3B2w9@unreal>

Thank you for the tip.
 -- Yajun

March 9, 2022 5:21 PM, "Leon Romanovsky" <leonro@nvidia.com> wrote:

> On Tue, Mar 08, 2022 at 10:34:28PM +0800, Yajun Deng wrote:
> 
>> 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.
> 
> 1. Please read commit message and content of commit 676a80adba01
> ("RDMA: Remove AH from uverbs_cmd_mask") that added that .create_user_ah()
> callback.
> 2. You should send patches as a series that is threaded and not as
> stand-alone patches.
> 
> Thanks

      reply	other threads:[~2022-03-09  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 14:34 [PATCH for-next 0/9] RDMA: get rid of create_user_ah Yajun Deng
2022-03-09  9:21 ` Leon Romanovsky
2022-03-09  9:34   ` Yajun Deng [this message]

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=9e6973cfbca0ef70bfd57f499a7f5397@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