From: Leon Romanovsky <leon@kernel.org>
To: Haoyue Xu <xuhaoyue1@hisilicon.com>
Cc: jgg@nvidia.com, linux-rdma@vger.kernel.org, linuxarm@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-next 0/3] Refactor rq inline and add cqe inline
Date: Wed, 28 Dec 2022 14:28:25 +0200 [thread overview]
Message-ID: <Y6w2aRPSXAv4s5Pp@unreal> (raw)
In-Reply-To: <20221224102201.3114536-1-xuhaoyue1@hisilicon.com>
On Sat, Dec 24, 2022 at 06:21:58PM +0800, Haoyue Xu wrote:
> The patchset mainly removes the kernel space
> rq inline features and supports cqe inline in user space.
>
> Luoyouming (3):
> RDMA/hns: Remove rq inline in kernel
> RDMA/hns: Add compatibility handling for only support userspace rq
> inline
> RDMA/hns: Support cqe inline in user space
>
> drivers/infiniband/hw/hns/hns_roce_device.h | 19 +---
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 109 ++++++--------------
> drivers/infiniband/hw/hns/hns_roce_hw_v2.h | 3 +-
> drivers/infiniband/hw/hns/hns_roce_main.c | 12 +++
> drivers/infiniband/hw/hns/hns_roce_qp.c | 66 +-----------
> include/uapi/rdma/hns-abi.h | 4 +
Your commit messages are too scarce for patches which touch UAPI.
Please add more details about why you deleted, what users should do next
and what are the features you are adding,
Thanks
> 6 files changed, 54 insertions(+), 159 deletions(-)
>
> --
> 2.30.0
>
next prev parent reply other threads:[~2022-12-28 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 10:21 [PATCH for-next 0/3] Refactor rq inline and add cqe inline Haoyue Xu
2022-12-24 10:21 ` [PATCH for-next 1/3] RDMA/hns: Remove rq inline in kernel Haoyue Xu
2022-12-24 10:22 ` [PATCH for-next 2/3] RDMA/hns: Add compatibility handling for only support userspace rq inline Haoyue Xu
2022-12-24 10:22 ` [PATCH for-next 3/3] RDMA/hns: Support cqe inline in user space Haoyue Xu
2022-12-28 12:28 ` Leon Romanovsky [this message]
2023-01-20 9:14 ` [PATCH for-next 0/3] Refactor rq inline and add cqe inline xuhaoyue (A)
2023-01-22 12:12 ` Leon Romanovsky
2023-01-09 15:03 ` Jason Gunthorpe
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=Y6w2aRPSXAv4s5Pp@unreal \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=xuhaoyue1@hisilicon.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).