From: Christoph Hellwig <hch@lst.de>
To: 廖亨权 <liaohengquan1986@163.com>
Cc: Keith Busch <keith.busch@intel.com>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 4/5] nvme: move the retries count to struct nvme_request
Date: Thu, 6 Apr 2017 10:38:26 +0200 [thread overview]
Message-ID: <20170406083826.GA32535@lst.de> (raw)
In-Reply-To: <5a5f1f1.8f7d.15b4267e21e.Coremail.liaohengquan1986@163.com>
On Thu, Apr 06, 2017 at 04:35:56PM +0800, 廖亨权 wrote:
> Hi, Guys,
> I want to ask if there is any plan to plant the NVMe driver to Vxworks OS?Thank you so much.---end quoted text---
The Linux NVMe team has no plans for a Vxworks NVMe driver at the moment.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 4/5] nvme: move the retries count to struct nvme_request
Date: Thu, 6 Apr 2017 10:38:26 +0200 [thread overview]
Message-ID: <20170406083826.GA32535@lst.de> (raw)
In-Reply-To: <5a5f1f1.8f7d.15b4267e21e.Coremail.liaohengquan1986@163.com>
On Thu, Apr 06, 2017@04:35:56PM +0800, ??? wrote:
> Hi, Guys,
> I want to ask if there is any plan to plant the NVMe driver to Vxworks OS?Thank you so much.---end quoted text---
The Linux NVMe team has no plans for a Vxworks NVMe driver at the moment.
next prev parent reply other threads:[~2017-04-06 8:38 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 14:18 ->retries fixups Christoph Hellwig
2017-04-05 14:18 ` Christoph Hellwig
2017-04-05 14:18 ` [PATCH 1/5] nvme: move ->retries setup to nvme_setup_cmd Christoph Hellwig
2017-04-05 14:18 ` Christoph Hellwig
2017-04-05 14:43 ` Johannes Thumshirn
2017-04-05 14:43 ` Johannes Thumshirn
2017-04-05 14:43 ` Johannes Thumshirn
2017-04-05 14:50 ` Christoph Hellwig
2017-04-05 14:50 ` Christoph Hellwig
2017-04-05 14:18 ` [PATCH 2/5] nvme: cleanup nvme_req_needs_retry Christoph Hellwig
2017-04-05 14:18 ` Christoph Hellwig
2017-04-05 14:42 ` Johannes Thumshirn
2017-04-05 14:42 ` Johannes Thumshirn
2017-04-05 14:42 ` Johannes Thumshirn
2017-04-05 14:18 ` [PATCH 3/5] nvme: mark nvme_max_retries static Christoph Hellwig
2017-04-05 14:18 ` Christoph Hellwig
2017-04-05 14:44 ` Johannes Thumshirn
2017-04-05 14:44 ` Johannes Thumshirn
2017-04-05 14:44 ` Johannes Thumshirn
2017-04-05 14:18 ` [PATCH 4/5] nvme: move the retries count to struct nvme_request Christoph Hellwig
2017-04-05 14:18 ` Christoph Hellwig
2017-04-05 14:45 ` Johannes Thumshirn
2017-04-05 14:45 ` Johannes Thumshirn
2017-04-05 14:45 ` Johannes Thumshirn
2017-04-05 15:14 ` Keith Busch
2017-04-05 15:14 ` Keith Busch
2017-04-05 15:25 ` Christoph Hellwig
2017-04-05 15:25 ` Christoph Hellwig
2017-04-06 8:35 ` 廖亨权
2017-04-06 8:38 ` Christoph Hellwig [this message]
2017-04-06 8:38 ` Christoph Hellwig
2017-04-05 14:18 ` [PATCH 5/5] block, scsi: move the retries field to struct scsi_request Christoph Hellwig
2017-04-05 14:18 ` Christoph Hellwig
2017-04-05 14:46 ` Johannes Thumshirn
2017-04-05 14:46 ` Johannes Thumshirn
2017-04-05 14:46 ` Johannes Thumshirn
2017-04-05 17:18 ->retries fixups V2 Christoph Hellwig
2017-04-05 17:18 ` [PATCH 4/5] nvme: move the retries count to struct nvme_request Christoph Hellwig
2017-04-05 17:18 ` Christoph Hellwig
2017-04-05 17:33 ` Sagi Grimberg
2017-04-05 17:33 ` 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=20170406083826.GA32535@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=keith.busch@intel.com \
--cc=liaohengquan1986@163.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.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.