From: Sagi Grimberg <sagi@grimberg.me>
To: zhenwei pi <pizhenwei@bytedance.com>,
kbusch@kernel.org, axboe@fb.com, hch@lst.de
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
lengchao@huawei.com
Subject: Re: [PATCH v3] nvme-rdma: handle nvme completion data length
Date: Mon, 26 Oct 2020 00:40:06 -0700 [thread overview]
Message-ID: <146e7680-264e-7b70-0a5c-a6e7dd520a2d@grimberg.me> (raw)
In-Reply-To: <20201025115124.1430678-1-pizhenwei@bytedance.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
WARNING: multiple messages have this Message-ID (diff)
From: Sagi Grimberg <sagi@grimberg.me>
To: zhenwei pi <pizhenwei@bytedance.com>,
kbusch@kernel.org, axboe@fb.com, hch@lst.de
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
lengchao@huawei.com
Subject: Re: [PATCH v3] nvme-rdma: handle nvme completion data length
Date: Mon, 26 Oct 2020 00:40:06 -0700 [thread overview]
Message-ID: <146e7680-264e-7b70-0a5c-a6e7dd520a2d@grimberg.me> (raw)
In-Reply-To: <20201025115124.1430678-1-pizhenwei@bytedance.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-10-26 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 11:51 [PATCH v3] nvme-rdma: handle nvme completion data length zhenwei pi
2020-10-25 11:51 ` zhenwei pi
2020-10-26 7:40 ` Sagi Grimberg [this message]
2020-10-26 7:40 ` Sagi Grimberg
2020-10-27 9:07 ` Christoph Hellwig
2020-10-27 9:07 ` Christoph Hellwig
2020-10-28 16:58 ` Max Gurtovoy
2020-10-28 16:58 ` Max Gurtovoy
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=146e7680-264e-7b70-0a5c-a6e7dd520a2d@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=lengchao@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=pizhenwei@bytedance.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.