From: Jason Gunthorpe <jgg@ziepe.ca>
To: Lijun Ou <oulijun@huawei.com>
Cc: dledford@redhat.com, leon@kernel.org, linux-rdma@vger.kernel.org,
linuxarm@huawei.com
Subject: Re: [PATCH for-next 0/8] Some fixes from hns
Date: Fri, 5 Jul 2019 14:23:51 -0300 [thread overview]
Message-ID: <20190705172351.GA7234@ziepe.ca> (raw)
In-Reply-To: <1561376872-111496-1-git-send-email-oulijun@huawei.com>
On Mon, Jun 24, 2019 at 07:47:44PM +0800, Lijun Ou wrote:
> Here are some bug fixes as well code optimization.
>
> Lang Cheng (3):
> RDMA/hns: Set reset flag when hw resetting
> RDMA/hns: Use %pK format pointer print
> RDMA/hns: Clean up unnecessary variable initialization
>
> Lijun Ou (1):
> RDMA/hns: Bugfix for cleaning mtr
>
> Xi Wang (1):
> RDMA/hns: Fixs hw access invalid dma memory error
>
> Yangyang Li (1):
> RDMA/hns: Modify ba page size for cqe
>
> chenglang (1):
> RDMA/hns: Fixup qp release bug
>
> o00290482 (1):
> RDMA/hns: Bugfix for calculating qp buffer size
>
> drivers/infiniband/hw/hns/hns_roce_cmd.c | 2 +-
> drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 4 +++-
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 9 +++++----
> drivers/infiniband/hw/hns/hns_roce_main.c | 2 +-
> drivers/infiniband/hw/hns/hns_roce_pd.c | 2 +-
> drivers/infiniband/hw/hns/hns_roce_qp.c | 13 ++++---------
> 6 files changed, 15 insertions(+), 17 deletions(-)
>
Applied to for-next, thanks
Jason
next parent reply other threads:[~2019-07-05 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1561376872-111496-1-git-send-email-oulijun@huawei.com>
2019-07-05 17:23 ` Jason Gunthorpe [this message]
[not found] ` <1561376872-111496-6-git-send-email-oulijun@huawei.com>
2019-07-06 1:47 ` [PATCH for-next 5/8] RDMA/hns: Bugfix for calculating qp buffer size oulijun
2019-07-07 12:21 ` Jason Gunthorpe
2019-07-08 13:46 ` oulijun
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=20190705172351.GA7234@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--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