From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Weihang Li <liweihang@huawei.com>,
dledford@redhat.com, linux-rdma@vger.kernel.org,
linuxarm@huawei.com
Subject: Re: [PATCH for-next 0/9] RDMA/hns: Cleanups for 5.8
Date: Mon, 25 May 2020 20:36:04 +0300 [thread overview]
Message-ID: <20200525173604.GG10591@unreal> (raw)
In-Reply-To: <20200525171116.GA17025@ziepe.ca>
On Mon, May 25, 2020 at 02:11:16PM -0300, Jason Gunthorpe wrote:
> On Wed, May 20, 2020 at 09:53:10PM +0800, Weihang Li wrote:
> > These are some cleanups, include removing dead code, modifying
> > varibles/fields types, and optimizing some functions.
> >
> > Lang Cheng (3):
> > RDMA/hns: Let software PI/CI grow naturally
> > RDMA/hns: Add CQ flag instead of independent enable flag
> > RDMA/hns: Optimize post and poll process
> >
> > Weihang Li (2):
> > RDMA/hns: Change all page_shift to unsigned
> > RDMA/hns: Change variables representing quantity to unsigned
> >
> > Xi Wang (3):
> > RDMA/hns: Rename QP buffer related function
> > RDMA/hns: Refactor the QP context filling process related to WQE
> > buffer configure
> > RDMA/hns: Optimize the usage of MTR
> >
> > Yangyang Li (1):
> > RDMA/hns: Remove unused code about assert
>
> I'm going to take these anyhow, the field macros could be improved
> someday if someone wanted. Applied to for-next
>
> I have to say the patches coming lately from hns have been following
> the kernel style and protocols much better. I'm also having a much
> easier time understanding the commit message and what the patch is
> trying to do. Keep it up!
+1, I have same feeling.
Thanks
>
> Thanks,
> Jason
next prev parent reply other threads:[~2020-05-25 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 13:53 [PATCH for-next 0/9] RDMA/hns: Cleanups for 5.8 Weihang Li
2020-05-20 13:53 ` [PATCH for-next 1/9] RDMA/hns: Let software PI/CI grow naturally Weihang Li
2020-05-20 13:53 ` [PATCH for-next 2/9] RDMA/hns: Add CQ flag instead of independent enable flag Weihang Li
2020-05-25 17:06 ` Jason Gunthorpe
2020-05-26 2:57 ` liweihang
2020-05-26 12:08 ` Jason Gunthorpe
2020-05-28 1:15 ` liweihang
2020-05-20 13:53 ` [PATCH for-next 3/9] RDMA/hns: Optimize post and poll process Weihang Li
2020-05-20 13:53 ` [PATCH for-next 4/9] RDMA/hns: Remove unused code about assert Weihang Li
2020-05-20 13:53 ` [PATCH for-next 5/9] RDMA/hns: Rename QP buffer related function Weihang Li
2020-05-20 13:53 ` [PATCH for-next 6/9] RDMA/hns: Change all page_shift to unsigned Weihang Li
2020-05-20 13:53 ` [PATCH for-next 7/9] RDMA/hns: Change variables representing quantity " Weihang Li
2020-05-20 13:53 ` [PATCH for-next 8/9] RDMA/hns: Refactor the QP context filling process related to WQE buffer configure Weihang Li
2020-05-20 13:53 ` [PATCH for-next 9/9] RDMA/hns: Optimize the usage of MTR Weihang Li
2020-05-25 17:11 ` [PATCH for-next 0/9] RDMA/hns: Cleanups for 5.8 Jason Gunthorpe
2020-05-25 17:36 ` Leon Romanovsky [this message]
2020-05-26 3:13 ` liweihang
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=20200525173604.GG10591@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--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).