From: Leon Romanovsky <leon@kernel.org>
To: Wenpeng Liang <liangwenpeng@huawei.com>
Cc: jgg@nvidia.com, linux-rdma@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH v2 rdma-core 1/2] Update kernel headers
Date: Wed, 17 Nov 2021 16:24:00 +0200 [thread overview]
Message-ID: <YZUQgOCq1ENw8Uy0@unreal> (raw)
In-Reply-To: <0fc3c207-afaa-7f64-3f93-d633b7ba5636@huawei.com>
On Tue, Nov 16, 2021 at 11:31:00PM +0800, Wenpeng Liang wrote:
>
> On 2021/11/16 23:03, Wenpeng Liang wrote:
> > To commit ?? ("RDMA/hns: Support direct wqe of userspace").
> >
> > Signed-off-by: Wenpeng Liang <liangwenpeng@huawei.com>
> > ---
> > kernel-headers/rdma/hns-abi.h | 2 ++
> > kernel-headers/rdma/rdma_netlink.h | 5 +++++
> > kernel-headers/rdma/rdma_user_rxe.h | 14 +++++++++++---
> > 3 files changed, 18 insertions(+), 3 deletions(-)
>
> Hi Leon,
>
> I have encountered a problem and I hope to master a correct
> submission method.
>
> This user space patch modifies the hns-abi.h file, so I use the
> python command to generate the patch to keep the kernel-headers
> consistent with the kernel mode:
>
> python3.5 kernel-headers/update --not-final <kernel space dir> <commitID>
>
> In addition to the modification of hns-abi.h, the generated patch
> also involves the modification of other files. And resulted in the
> following compilation error:
>
> /rdma-core/providers/rxe/rxe.c: In function ‘rxe_post_one_recv’:
> /rdma-core/providers/rxe/rxe.c:712:17: error: ‘struct rxe_dma_info’ has no member named ‘sge’
> 712 | memcpy(wqe->dma.sge, recv_wr->sg_list,
> | ^
> /rdma-core/providers/rxe/rxe.c:713:38: error: ‘struct rxe_dma_info’ has no member named ‘sge’
> 713 | wqe->num_sge*sizeof(*wqe->dma.sge));
>
> In this case, what is the correct way to submit the patch? Should
> I wait for the rxe patch submission to complete before submitting
> this patchset, or submit only the hns part of the patch generated
> by python?
Please wait a couple of days, we will fix Jason's PR and I will release
rdma-core, so you will be able to submit without errors.
Thanks
>
> Thanks,
> Wenpeng
next prev parent reply other threads:[~2021-11-17 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 15:03 [PATCH v2 rdma-core 0/2] libhns: Add support for direct wqe Wenpeng Liang
2021-11-16 15:03 ` [PATCH v2 rdma-core 1/2] Update kernel headers Wenpeng Liang
2021-11-16 15:31 ` Wenpeng Liang
2021-11-16 19:57 ` Jason Gunthorpe
2021-11-17 14:24 ` Leon Romanovsky [this message]
2021-11-16 15:03 ` [PATCH v2 rdma-core 2/2] libhns: Add support for direct wqe Wenpeng Liang
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=YZUQgOCq1ENw8Uy0@unreal \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=liangwenpeng@huawei.com \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@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