From: Jason Gunthorpe <jgg@nvidia.com>
To: Xiao Yang <yangx.jy@fujitsu.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>,
"leon@kernel.org" <leon@kernel.org>,
"lizhijian@fujitsu.com" <lizhijian@fujitsu.com>,
"y-goto@fujitsu.com" <y-goto@fujitsu.com>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>
Subject: Re: [PATCH v6 0/8] RDMA/rxe: Add atomic write operation
Date: Thu, 1 Dec 2022 10:45:55 -0400 [thread overview]
Message-ID: <Y4i+I5P1GApq48hR@nvidia.com> (raw)
In-Reply-To: <5fa61fdf-b161-7699-c551-164be118d80c@fujitsu.com>
On Thu, Dec 01, 2022 at 10:16:15PM +0800, Xiao Yang wrote:
> On 2022/12/1 20:58, Jason Gunthorpe wrote:
> > It is not really "empty line" it is that the last character in the
> > file should be '\n', and all files are like that.
> Hi Jason,
>
> Thanks for your explanation.
>
> I think my latest patch has added an "empty line", right?
yes
Jason
prev parent reply other threads:[~2022-12-01 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 6:37 [PATCH v6 0/8] RDMA/rxe: Add atomic write operation yangx.jy
2022-10-15 6:37 ` [PATCH v6 2/8] RDMA: Extend RDMA kernel ABI to support atomic write yangx.jy
2022-10-15 6:37 ` [PATCH v6 1/8] RDMA: Extend RDMA user " yangx.jy
2022-11-22 19:49 ` Jason Gunthorpe
2022-12-01 11:04 ` Xiao Yang
2022-10-15 6:37 ` [PATCH v6 3/8] RDMA/rxe: Extend rxe " yangx.jy
2022-10-15 6:37 ` [PATCH v6 4/8] RDMA/rxe: Extend rxe packet format " yangx.jy
2022-10-15 6:37 ` [PATCH v6 5/8] RDMA/rxe: Make requester support atomic write on RC service yangx.jy
2022-10-15 6:37 ` [PATCH v6 6/8] RDMA/rxe: Make responder " yangx.jy
2022-10-15 6:37 ` [PATCH v6 7/8] RDMA/rxe: Implement atomic write completion yangx.jy
2022-10-15 6:37 ` [PATCH v6 8/8] RDMA/rxe: Enable atomic write capability for rxe device yangx.jy
2022-10-15 8:41 ` [PATCH v6 0/8] RDMA/rxe: Add atomic write operation Yang, Xiao/杨 晓
2022-11-22 19:54 ` Jason Gunthorpe
2022-12-01 11:58 ` Xiao Yang
2022-12-01 12:58 ` Jason Gunthorpe
2022-12-01 14:16 ` Xiao Yang
2022-12-01 14:45 ` Jason Gunthorpe [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=Y4i+I5P1GApq48hR@nvidia.com \
--to=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=yangx.jy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.