All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Weihang Li <liweihang@huawei.com>
Cc: <dledford@redhat.com>, <leon@kernel.org>,
	<linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>
Subject: Re: [PATCH v2 for-next] RDMA/hns: Move capability flags of QP and CQ to hns-abi.h
Date: Mon, 7 Dec 2020 15:51:37 -0400	[thread overview]
Message-ID: <20201207195137.GA1786195@nvidia.com> (raw)
In-Reply-To: <1606872560-17823-1-git-send-email-liweihang@huawei.com>

On Wed, Dec 02, 2020 at 09:29:20AM +0800, Weihang Li wrote:
> These flags will be returned to the userspace through ABI, so they should
> be defined in hns-abi.h. Furthermore, there is no need to include
> hns-abi.h in every source files, it just needs to be included in the
> common header file.
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Weihang Li <liweihang@huawei.com>
> ---
> Changes since v1:
> - Replace 'BIT(x)' with '1 << x'.
> 
> Previous Version:
> v1: https://patchwork.kernel.org/project/linux-rdma/patch/1606829024-51856-1-git-send-email-liweihang@huawei.com/
> 
>  drivers/infiniband/hw/hns/hns_roce_cq.c     |  1 -
>  drivers/infiniband/hw/hns/hns_roce_device.h | 11 +----------
>  drivers/infiniband/hw/hns/hns_roce_main.c   |  1 -
>  drivers/infiniband/hw/hns/hns_roce_pd.c     |  1 -
>  drivers/infiniband/hw/hns/hns_roce_qp.c     |  1 -
>  drivers/infiniband/hw/hns/hns_roce_srq.c    |  1 -
>  include/uapi/rdma/hns-abi.h                 | 10 ++++++++++
>  7 files changed, 11 insertions(+), 15 deletions(-)

Applied to for-next, thanks

Jason

      reply	other threads:[~2020-12-07 19:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02  1:29 [PATCH v2 for-next] RDMA/hns: Move capability flags of QP and CQ to hns-abi.h Weihang Li
2020-12-07 19:51 ` Jason Gunthorpe [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=20201207195137.GA1786195@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=dledford@redhat.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liweihang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.