public inbox for linux-rdma@vger.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 v5 for-next 0/9] RDMA/hns: Use new interfaces to write/read fields
Date: Mon, 21 Jun 2021 15:37:18 -0300	[thread overview]
Message-ID: <20210621183718.GA2338038@nvidia.com> (raw)
In-Reply-To: <1624262443-24528-1-git-send-email-liweihang@huawei.com>

On Mon, Jun 21, 2021 at 04:00:34PM +0800, Weihang Li wrote:
> hr_reg_*() is simpler than roce_set_*(), and the field/bit can be generated
> automatically and accurately. This series first fixes two issues on
> hr_reg_*(), then introduces hr_reg_write_bool() for 1 bit-width field, does
> the replacement at last.
> 
> Changes since v4:
> * Change the way to fix the sparse warning, we introduce
>   hr_reg_write_bool() for 1 bit-width field.
> * Link: https://patchwork.kernel.org/project/linux-rdma/cover/1624010765-1029-1-git-send-email-liweihang@huawei.com/
> 
> Changes since v3:
> * Use "val ? 1 : 0" instead of "!!val" for hr_reg_write to avoid sparse
>   warnings.
> * Link: https://patchwork.kernel.org/project/linux-rdma/cover/1623915111-43630-1-git-send-email-liweihang@huawei.com/
> 
> Changes since v2:
> * Add a patch to solve the gcc warnings about PREP_FIELD() by adding a
>   check for mtu. Therefore only the parts which fix the sparse warning is
>   reserved in #1.
> * Link: https://patchwork.kernel.org/project/linux-rdma/cover/1622624265-44796-1-git-send-email-liweihang@huawei.com/
> 
> Changes since v1:
> * Add a patch to fix gcc warnings about PREP_FIELD().
> * Fix a typo in #5.
> * Link: https://patchwork.kernel.org/project/linux-rdma/cover/1622281154-49867-1-git-send-email-liweihang@huawei.com/
> 
> Lang Cheng (3):
>   RDMA/hns: Add hr_reg_write_bool()
>   RDMA/hns: Use new interface to modify QP context
>   RDMA/hns: Use new interface to get CQE fields
> 
> Weihang Li (2):
>   RDMA/hns: Fix sparse warnings when calling hr_reg_write()
>   RDMA/hns: Add a check to ensure integer mtu is positive
> 
> Xi Wang (1):
>   RDMA/hns: Clean SRQC structure definition
> 
> Yixing Liu (3):
>   RDMA/hns: Use new interface to write CQ context.
>   RDMA/hns: Use new interface to write FRMR fields
>   RDMA/hns: Use new interface to write DB related fields

Applied to for-next, thanks

Jason

      parent reply	other threads:[~2021-06-21 18:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21  8:00 [PATCH v5 for-next 0/9] RDMA/hns: Use new interfaces to write/read fields Weihang Li
2021-06-21  8:00 ` [PATCH v5 for-next 1/9] RDMA/hns: Fix sparse warnings when calling hr_reg_write() Weihang Li
2021-06-21  8:00 ` [PATCH v5 for-next 2/9] RDMA/hns: Add a check to ensure integer mtu is positive Weihang Li
2021-06-21  8:00 ` [PATCH v5 for-next 3/9] RDMA/hns: Add hr_reg_write_bool() Weihang Li
2021-06-21  8:00 ` [PATCH v5 for-next 4/9] RDMA/hns: Use new interface to write CQ context Weihang Li
2021-06-21  8:00 ` [PATCH v5 for-next 5/9] RDMA/hns: Use new interface to modify QP context Weihang Li
2021-06-21  8:00 ` [PATCH v5 for-next 6/9] RDMA/hns: Use new interface to get CQE fields Weihang Li
2021-06-21  8:00 ` [PATCH v5 for-next 7/9] RDMA/hns: Use new interface to write FRMR fields Weihang Li
2021-06-21  8:00 ` [PATCH v5 for-next 8/9] RDMA/hns: Use new interface to write DB related fields Weihang Li
2021-06-21  8:00 ` [PATCH v5 for-next 9/9] RDMA/hns: Clean SRQC structure definition Weihang Li
2021-06-21 18:37 ` 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=20210621183718.GA2338038@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox