From: "Engel, Amit" <Amit.Engel@Dell.com>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Sagi Grimberg <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: RE: [PATCH] nvmet: return Invalid Field error on set features cmd fid 07h
Date: Sun, 1 Mar 2020 04:47:26 +0000 [thread overview]
Message-ID: <MN2PR19MB30058A102F30C99029F1FC38EEE60@MN2PR19MB3005.namprd19.prod.outlook.com> (raw)
In-Reply-To: <BYAPR04MB57499DC82E126AEAD6682B3C86E60@BYAPR04MB5749.namprd04.prod.outlook.com>
Thank you
-----Original Message-----
From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Sent: Sunday, March 1, 2020 2:30 AM
To: Sagi Grimberg; Engel, Amit; linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet: return Invalid Field error on set features cmd fid 07h
[EXTERNAL EMAIL]
Sent out a patch with following comments and appropriate history.
On 02/28/2020 12:33 PM, Sagi Grimberg wrote:
> I meant that here we only declare, assignment should go to where these
> are used.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-03-01 4:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 12:52 [PATCH] nvmet: return Invalid Field error on set features cmd fid 07h amit.engel
2020-02-28 20:33 ` Sagi Grimberg
2020-03-01 0:30 ` Chaitanya Kulkarni
2020-03-01 4:47 ` Engel, Amit [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-27 14:16 amit.engel
2020-02-27 23:16 ` Sagi Grimberg
2020-02-28 12:53 ` Engel, Amit
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=MN2PR19MB30058A102F30C99029F1FC38EEE60@MN2PR19MB3005.namprd19.prod.outlook.com \
--to=amit.engel@dell.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=linux-nvme@lists.infradead.org \
--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 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.