From: Xiao Yang <yangx.jy@fujitsu.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: <linux-rdma@vger.kernel.org>, <rpearsonhpe@gmail.com>,
<leon@kernel.org>, <lizhijian@fujitsu.com>, <y-goto@fujitsu.com>,
<zyjzyj2000@gmail.com>
Subject: Re: [PATCH v7 0/8] RDMA/rxe: Add atomic write operation
Date: Fri, 2 Dec 2022 13:37:59 +0800 [thread overview]
Message-ID: <949b84bf-b865-a407-b572-d9433082bec4@fujitsu.com> (raw)
In-Reply-To: <Y4k/DKgScOz9vpVc@nvidia.com>
On 2022/12/2 7:55, Jason Gunthorpe wrote:
> On Thu, Dec 01, 2022 at 02:37:04PM +0000, Xiao Yang wrote:
>
>> Xiao Yang (8):
>> RDMA: Extend RDMA user ABI to support atomic write
>> RDMA: Extend RDMA kernel ABI to support atomic write
>> RDMA/rxe: Extend rxe user ABI to support atomic write
>> RDMA/rxe: Extend rxe packet format to support atomic write
>> RDMA/rxe: Make requester support atomic write on RC service
>> RDMA/rxe: Make responder support atomic write on RC service
>> RDMA/rxe: Implement atomic write completion
>> RDMA/rxe: Enable atomic write capability for rxe device
>
> Applied to for-next, thanks
>
> Jason
Hi Jason,
Cool, Thank you very much for reviewing and applying the patch set.
Besides, I have removed the rdma_atomic_write example as you suggested
on rdma-core repo.
Best Regards,
Xiao Yang
prev parent reply other threads:[~2022-12-02 5:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 14:37 [PATCH v7 0/8] RDMA/rxe: Add atomic write operation Xiao Yang
2022-12-01 14:37 ` [PATCH v7 1/8] RDMA: Extend RDMA user ABI to support atomic write Xiao Yang
2022-12-01 14:37 ` [PATCH v7 2/8] RDMA: Extend RDMA kernel " Xiao Yang
2022-12-01 14:37 ` [PATCH v7 3/8] RDMA/rxe: Extend rxe user " Xiao Yang
2022-12-01 14:37 ` [PATCH v7 4/8] RDMA/rxe: Extend rxe packet format " Xiao Yang
2022-12-01 23:55 ` [PATCH v7 0/8] RDMA/rxe: Add atomic write operation Jason Gunthorpe
2022-12-02 5:37 ` Xiao Yang [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=949b84bf-b865-a407-b572-d9433082bec4@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=rpearsonhpe@gmail.com \
--cc=y-goto@fujitsu.com \
--cc=zyjzyj2000@gmail.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