linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagi@grimberg.me>
To: Max Gurtovoy <maxg@mellanox.com>,
	"jianchao.wang" <jianchao.w.wang@oracle.com>,
	keith.busch@intel.com, axboe@fb.com, hch@lst.de
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [Suspected-Phishing]Re: [PATCH V3 1/2] nvme: split resetting state into reset_prepate and resetting
Date: Wed, 17 Jan 2018 14:02:24 +0200	[thread overview]
Message-ID: <bc1e56bd-84fe-0bab-57eb-1f8b691ea19e@grimberg.me> (raw)
In-Reply-To: <87bc4cf6-8f69-0f49-2196-d8e8a27e3223@mellanox.com>

> see V4 discussion.. :)

I didn't see any v4

  parent reply	other threads:[~2018-01-17 12:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11  5:07 [PATCH V3 0/2] nvme-pci: fix the timeout case when reset is ongoing Jianchao Wang
2018-01-11  5:07 ` [PATCH V3 1/2] nvme: split resetting state into reset_prepate and resetting Jianchao Wang
2018-01-14  9:48   ` Sagi Grimberg
2018-01-15  2:02     ` jianchao.wang
2018-01-15  2:11       ` Keith Busch
2018-01-15  2:31         ` jianchao.wang
2018-01-15 13:28     ` Max Gurtovoy
2018-01-15 13:36       ` [Suspected-Phishing]Re: " Max Gurtovoy
2018-01-16  5:57         ` jianchao.wang
2018-01-16  7:52           ` jianchao.wang
2018-01-17 10:37           ` Sagi Grimberg
     [not found]             ` <87bc4cf6-8f69-0f49-2196-d8e8a27e3223@mellanox.com>
2018-01-17 12:02               ` Sagi Grimberg [this message]
2018-01-17 21:08             ` James Smart
2018-01-18  3:24               ` jianchao.wang
2018-01-15 14:07       ` jianchao.wang
2018-01-11  5:07 ` [PATCH V3 2/2] nvme-pci: fix the timeout case when reset is ongoing Jianchao Wang
2018-01-14  9:49   ` 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=bc1e56bd-84fe-0bab-57eb-1f8b691ea19e@grimberg.me \
    --to=sagi@grimberg.me \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=jianchao.w.wang@oracle.com \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=maxg@mellanox.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 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).