linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Engel, Amit" <Amit.Engel@Dell.com>
To: Christoph Hellwig <hch@infradead.org>,
	"sagi@grimberg.me" <sagi@grimberg.me>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: RE: [PATCH] nvmet: fix a wrong error status returned in error log page
Date: Wed, 11 Sep 2019 19:19:30 +0000	[thread overview]
Message-ID: <8739B0CD2FC2DC40AF691A1CCBB9896034611F97@MX302CL04.corp.emc.com> (raw)
In-Reply-To: <8739B0CD2FC2DC40AF691A1CCBB9896034610EBC@MX302CL04.corp.emc.com>

Hi Christoph/Sagi,

Any estimation when this patch will be pushed upstream officially?

Thanks
Amit

-----Original Message-----
From: Engel, Amit 
Sent: Wednesday, September 4, 2019 9:41 PM
To: 'Christoph Hellwig'
Cc: sagi@grimberg.me; linux-nvme@lists.infradead.org
Subject: RE: [PATCH] nvmet: fix a wrong error status returned in error log page

Ok, Done

Thanks
Amit

-----Original Message-----
From: Christoph Hellwig <hch@infradead.org> 
Sent: Wednesday, September 4, 2019 6:20 PM
To: Engel, Amit
Cc: Christoph Hellwig; sagi@grimberg.me; linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet: fix a wrong error status returned in error log page


[EXTERNAL EMAIL] 

On Wed, Sep 04, 2019 at 02:05:16PM +0000, Engel, Amit wrote:
> Should I provide a patch according to your suggestion?

Yes, please do.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2019-09-11 19:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-31 18:50 [PATCH] nvmet: fix a wrong error status returned in error log page amit.engel
2019-09-04 13:14 ` Christoph Hellwig
2019-09-04 14:05   ` Engel, Amit
2019-09-04 15:19     ` Christoph Hellwig
2019-09-04 18:40       ` Engel, Amit
2019-09-11 19:19         ` Engel, Amit [this message]
2019-09-11 19:44           ` Sagi Grimberg
2019-09-12  5:32             ` Engel, Amit
2019-09-12  5:29 amit.engel
2019-09-12 12:09 ` Christoph Hellwig
2019-09-12 15:50 ` Sagi Grimberg

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=8739B0CD2FC2DC40AF691A1CCBB9896034611F97@MX302CL04.corp.emc.com \
    --to=amit.engel@dell.com \
    --cc=hch@infradead.org \
    --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 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).