From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>, Christoph Hellwig <hch@lst.de>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 2/2] nvme: resync header file with common nvme-cli tool
Date: Mon, 15 Feb 2021 01:33:06 +0000 [thread overview]
Message-ID: <BYAPR04MB4965D9C2B54B8B01FEF26FE286889@BYAPR04MB4965.namprd04.prod.outlook.com> (raw)
In-Reply-To: BYAPR12MB34947F0C352E4035BAC258CFDE8C9@BYAPR12MB3494.namprd12.prod.outlook.com
On 2/11/21 05:02, Max Gurtovoy wrote:
> see attached.
>
> Btw, the nvme-5.12 is not so stable.
> I didn't debug it but I couldn't establish rdma/tcp/loop connections.
> So the attached was just compiled and not tested.
>
> -----Original Message-----
> From: Christoph Hellwig <hch@lst.de>
> Sent: Tuesday, February 9, 2021 5:35 PM
> To: Max Gurtovoy <mgurtovoy@nvidia.com>
> Cc: Christoph Hellwig <hch@lst.de>; linux-nvme@lists.infradead.org; sagi@grimberg.me; kbusch@kernel.org; chaitanya.kulkarni@wdc.com
> Subject: Re: [PATCH 2/2] nvme: resync header file with common nvme-cli tool
>
> On Tue, Feb 09, 2021 at 03:07:05PM +0000, Max Gurtovoy wrote:
>> is this respin still needed ?
> Yes.
>
FYI, I sent out the series with Max's attached patch as I needed that to
rebase some of my work, please have a look.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-02-15 1:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 9:09 [PATCH v2 0/2] Resync Linux and NVMe-cli nvme.h header Max Gurtovoy
2021-01-21 9:09 ` [PATCH nvme-cli 1/1] align Linux kernel nvme.h to nvme-cli Max Gurtovoy
2021-01-21 9:09 ` [PATCH 1/2] nvme: update enumerations for status codes Max Gurtovoy
2021-01-27 17:46 ` Christoph Hellwig
2021-01-21 9:09 ` [PATCH 2/2] nvme: resync header file with common nvme-cli tool Max Gurtovoy
2021-01-27 17:47 ` Christoph Hellwig
2021-02-09 15:07 ` Max Gurtovoy
2021-02-09 15:35 ` Christoph Hellwig
2021-02-11 13:01 ` Max Gurtovoy
2021-02-15 1:33 ` Chaitanya Kulkarni [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=BYAPR04MB4965D9C2B54B8B01FEF26FE286889@BYAPR04MB4965.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mgurtovoy@nvidia.com \
--cc=sagi@grimberg.me \
/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).