linux-rdma.vger.kernel.org archive mirror
 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 00/11] RDMA/hns: Updates for 5.11
Date: Fri, 11 Dec 2020 15:39:50 -0400	[thread overview]
Message-ID: <20201211193950.GA2222830@nvidia.com> (raw)
In-Reply-To: <1607650657-35992-1-git-send-email-liweihang@huawei.com>

On Fri, Dec 11, 2020 at 09:37:26AM +0800, Weihang Li wrote:
> There are miscellaneous updates for hns driver:
> * #1 fixes a potential length issue when copying udata.
> * #2 fixes the unreasonable judgment when using HEM of SRQ and SCCC.
> * #3 fixes wrong value of Traffic Class.
> * #4 and #5 fix issues about Service Level.
> * #6 ~ #11 are cleanups, including removing dead code, fixing coding style
>   issues and so on.
> 
> Changes since v4:
> - Fix a compiler error caused by #9.
> 
> Changes since v3:
> - Avoid an unused variable warning in #10.
> 
> Changes since v2:
> - Remove WARN_ON() in #5 when filling QPC.
> 
> Changes since v1:
> - Only do shift on tclass when using RoCEv2 in #3.
> 
> Previous version:
> v4: https://patchwork.kernel.org/project/linux-rdma/cover/1607608479-54518-1-git-send-email-liweihang@huawei.com/
> v3: https://patchwork.kernel.org/project/linux-rdma/cover/1607606572-11968-1-git-send-email-liweihang@huawei.com/
> v2: https://patchwork.kernel.org/project/linux-rdma/cover/1607078436-26455-1-git-send-email-liweihang@huawei.com/
> v1: https://patchwork.kernel.org/project/linux-rdma/cover/1606899553-54592-1-git-send-email-liweihang@huawei.com/
> 
> Lang Cheng (1):
>   RDMA/hns: Fix coding style issues
> 
> Weihang Li (3):
>   RDMA/hns: Do shift on traffic class when using RoCEv2
>   RDMA/hns: Avoid filling sl in high 3 bits of vlan_id
>   RDMA/hns: WARN_ON if get a reserved sl from users
> 
> Wenpeng Liang (3):
>   RDMA/hns: Limit the length of data copied between kernel and userspace
>   RDMA/hns: Normalization the judgment of some features
>   RDMA/hns: Fix incorrect symbol types
> 
> Xinhao Liu (1):
>   RDMA/hns: Clear redundant variable initialization
> 
> Yixian Liu (2):
>   RDMA/hns: Remove unnecessary access right set during INIT2INIT
>   RDMA/hns: Simplify AEQE process for different types of queue
> 
> Yixing Liu (1):
>   RDMA/hns: Fix inaccurate prints

Applied to for-next, thanks

Jason

      parent reply	other threads:[~2020-12-11 21:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  1:37 [PATCH v5 for-next 00/11] RDMA/hns: Updates for 5.11 Weihang Li
2020-12-11  1:37 ` [PATCH v5 for-next 01/11] RDMA/hns: Limit the length of data copied between kernel and userspace Weihang Li
2020-12-11  1:37 ` [PATCH v5 for-next 02/11] RDMA/hns: Normalization the judgment of some features Weihang Li
2020-12-11  1:37 ` [PATCH v5 for-next 03/11] RDMA/hns: Do shift on traffic class when using RoCEv2 Weihang Li
2020-12-11  1:37 ` [PATCH v5 for-next 04/11] RDMA/hns: Avoid filling sl in high 3 bits of vlan_id Weihang Li
2020-12-11  1:37 ` [PATCH v5 for-next 05/11] RDMA/hns: WARN_ON if get a reserved sl from users Weihang Li
2020-12-11  1:37 ` [PATCH v5 for-next 06/11] RDMA/hns: Remove unnecessary access right set during INIT2INIT Weihang Li
2020-12-11  1:37 ` [PATCH v5 for-next 07/11] RDMA/hns: Fix coding style issues Weihang Li
2020-12-11  1:37 ` [PATCH v5 for-next 08/11] RDMA/hns: Clear redundant variable initialization Weihang Li
2020-12-11  1:37 ` [PATCH v5 for-next 09/11] RDMA/hns: Fix incorrect symbol types Weihang Li
2020-12-11  1:37 ` [PATCH v5 for-next 10/11] RDMA/hns: Fix inaccurate prints Weihang Li
2020-12-11  1:37 ` [PATCH v5 for-next 11/11] RDMA/hns: Simplify AEQE process for different types of queue Weihang Li
2020-12-11 19:39 ` 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=20201211193950.GA2222830@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;
as well as URLs for NNTP newsgroup(s).