From: Doug Ledford <dledford@redhat.com>
To: Lijun Ou <oulijun@huawei.com>, jgg@ziepe.ca
Cc: linux-rdma@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH for-next 0/9] Fixes for hip08 driver
Date: Wed, 28 Aug 2019 11:31:00 -0400 [thread overview]
Message-ID: <d8f70a3e7bf0cd2da5873c75509dc39b0510c83d.camel@redhat.com> (raw)
In-Reply-To: <1566393276-42555-1-git-send-email-oulijun@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
On Wed, 2019-08-21 at 21:14 +0800, Lijun Ou wrote:
> Here optimizes some codes and removes some warnings
> by sparse tool checking as well as fixes some defects.
>
> Lang Cheng (3):
> RDMA/hns: Modify the data structure of hns_roce_av
> RDMA/hns: Fix cast from or to restricted __le32 for driver
> RDMA/hns: Add reset process for function-clear
>
> Lijun Ou (3):
> RDMA/hns: Refactor the codes of creating qp
> RDMA/hns: Remove the some magic number
> RDMA/hns: Fix wrong assignment of qp_access_flags
>
> Wenpeng Liang (2):
> RDMA/hns: Remove if-else judgment statements for creating srq
> RDMA/hns: Delete the not-used lines
>
> Yixian Liu (1):
> RDMA/hns: Refactor cmd init and mode selection for hip08
>
> drivers/infiniband/hw/hns/hns_roce_ah.c | 23 +--
> drivers/infiniband/hw/hns/hns_roce_cmd.c | 14 +-
> drivers/infiniband/hw/hns/hns_roce_device.h | 17 +-
> drivers/infiniband/hw/hns/hns_roce_hem.c | 34 ++--
> drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 49 +++---
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 256
> +++++++++++++++++++---------
> drivers/infiniband/hw/hns/hns_roce_hw_v2.h | 5 +-
> drivers/infiniband/hw/hns/hns_roce_main.c | 18 +-
> drivers/infiniband/hw/hns/hns_roce_mr.c | 7 +-
> drivers/infiniband/hw/hns/hns_roce_qp.c | 108 +++++++-----
> drivers/infiniband/hw/hns/hns_roce_srq.c | 30 +---
> 11 files changed, 314 insertions(+), 247 deletions(-)
>
I took patches 3-9 into for-next. Please fixup and resend 1 and 2.
Thanks.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-08-28 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 13:14 [PATCH for-next 0/9] Fixes for hip08 driver Lijun Ou
2019-08-21 13:14 ` [PATCH for-next 1/9] RDMA/hns: Refactor cmd init and mode selection for hip08 Lijun Ou
2019-08-21 17:19 ` Leon Romanovsky
2019-08-26 8:43 ` liweihang
2019-08-21 13:14 ` [PATCH for-next 2/9] RDMA/hns: Refactor the codes of creating qp Lijun Ou
2019-08-28 15:19 ` Doug Ledford
2019-08-29 0:56 ` oulijun
2019-08-21 13:14 ` [PATCH for-next 3/9] RDMA/hns: Modify the data structure of hns_roce_av Lijun Ou
2019-08-21 13:14 ` [PATCH for-next 4/9] RDMA/hns: Remove the some magic number Lijun Ou
2019-08-21 13:14 ` [PATCH for-next 5/9] RDMA/hns: Fix cast from or to restricted __le32 for driver Lijun Ou
2019-08-21 13:14 ` [PATCH for-next 6/9] RDMA/hns: Add reset process for function-clear Lijun Ou
2019-08-21 13:14 ` [PATCH for-next 7/9] RDMA/hns: Remove if-else judgment statements for creating srq Lijun Ou
2019-08-21 13:14 ` [PATCH for-next 8/9] RDMA/hns: Delete the not-used lines Lijun Ou
2019-08-21 13:14 ` [PATCH for-next 9/9] RDMA/hns: Fix wrong assignment of qp_access_flags Lijun Ou
2019-08-28 15:31 ` Doug Ledford [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=d8f70a3e7bf0cd2da5873c75509dc39b0510c83d.camel@redhat.com \
--to=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=oulijun@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).