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@openeuler.org>
Subject: Re: [PATCH v2 for-next 0/5] RDMA/hns: Fix and refactor CMDQ related code
Date: Tue, 9 Feb 2021 15:37:22 -0400 [thread overview]
Message-ID: <20210209193722.GA1339019@nvidia.com> (raw)
In-Reply-To: <1612688143-28226-1-git-send-email-liweihang@huawei.com>
On Sun, Feb 07, 2021 at 04:55:38PM +0800, Weihang Li wrote:
> Remove some dead code in process of CMDQ transmission, and fix an issue
> about missing error code.
>
> Changes since v1:
> * Drop #2 from the v1 series because the compatibility with the firmware
> needs to be considered.
> * Link: https://patchwork.kernel.org/project/linux-rdma/cover/1612419786-39173-1-git-send-email-liweihang@huawei.com/
>
> Lang Cheng (5):
> RDMA/hns: Remove unused member and variable of CMDQ
> RDMA/hns: Fixes missing error code of CMDQ
> RDMA/hns: Remove redundant operations on CMDQ
> RDMA/hns: Adjust fields and variables about CMDQ tail/head
> RDMA/hns: Refactor process of posting CMDQ
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2021-02-09 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 8:55 [PATCH v2 for-next 0/5] RDMA/hns: Fix and refactor CMDQ related code Weihang Li
2021-02-07 8:55 ` [PATCH v2 for-next 1/5] RDMA/hns: Remove unused member and variable of CMDQ Weihang Li
2021-02-07 8:55 ` [PATCH v2 for-next 2/5] RDMA/hns: Fixes missing error code " Weihang Li
2021-02-07 8:55 ` [PATCH v2 for-next 3/5] RDMA/hns: Remove redundant operations on CMDQ Weihang Li
2021-02-07 8:55 ` [PATCH v2 for-next 4/5] RDMA/hns: Adjust fields and variables about CMDQ tail/head Weihang Li
2021-02-07 8:55 ` [PATCH v2 for-next 5/5] RDMA/hns: Refactor process of posting CMDQ Weihang Li
2021-02-09 19: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=20210209193722.GA1339019@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--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.