From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme-pci: ensure nvme_timeout complete before initializing procedure
Date: Mon, 22 Jan 2018 21:14:23 +0100 [thread overview]
Message-ID: <20180122201423.GA30427@lst.de> (raw)
In-Reply-To: <1516607585-1525-1-git-send-email-jianchao.w.wang@oracle.com>
> Link: https://lkml.org/lkml/2018/1/19/68
> Suggested-by: Keith Busch <keith.busch at intel.com>
> Signed-off-by: Keith Busch <keith.busch at intel.com>
> Signed-off-by: Jianchao Wang <jianchao.w.wang at oracle.com>
Why does this have a signoff from Keith?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Jianchao Wang <jianchao.w.wang@oracle.com>
Cc: keith.busch@intel.com, axboe@fb.com, hch@lst.de,
sagi@grimberg.me, maxg@mellanox.com, james.smart@broadcom.com,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme-pci: ensure nvme_timeout complete before initializing procedure
Date: Mon, 22 Jan 2018 21:14:23 +0100 [thread overview]
Message-ID: <20180122201423.GA30427@lst.de> (raw)
In-Reply-To: <1516607585-1525-1-git-send-email-jianchao.w.wang@oracle.com>
> Link: https://lkml.org/lkml/2018/1/19/68
> Suggested-by: Keith Busch <keith.busch@intel.com>
> Signed-off-by: Keith Busch <keith.busch@intel.com>
> Signed-off-by: Jianchao Wang <jianchao.w.wang@oracle.com>
Why does this have a signoff from Keith?
next prev parent reply other threads:[~2018-01-22 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 7:53 [PATCH] nvme-pci: ensure nvme_timeout complete before initializing procedure Jianchao Wang
2018-01-22 7:53 ` Jianchao Wang
2018-01-22 20:14 ` Christoph Hellwig [this message]
2018-01-22 20:14 ` Christoph Hellwig
2018-01-22 21:54 ` Keith Busch
2018-01-22 21:54 ` Keith Busch
2018-01-23 1:43 ` jianchao.wang
2018-01-23 1:43 ` jianchao.wang
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=20180122201423.GA30427@lst.de \
--to=hch@lst.de \
/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.