All of lore.kernel.org
 help / color / mirror / Atom feed
From: 廖亨权 <liaohengquan1986@163.com>
To: "Keith Busch" <keith.busch@intel.com>
Cc: "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:Re: [PATCH 4/5] nvme: move the retries count to struct nvme_request
Date: Thu, 6 Apr 2017 16:35:56 +0800 (CST)	[thread overview]
Message-ID: <5a5f1f1.8f7d.15b4267e21e.Coremail.liaohengquan1986@163.com> (raw)
In-Reply-To: <20170405151430.GS20181@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 117 bytes --]

Hi, Guys,
              I want to ask if there is any plan to plant the NVMe driver to Vxworks OS?Thank  you so much.

[-- Attachment #2: Type: text/html, Size: 316 bytes --]

  parent reply	other threads:[~2017-04-06  8:35 UTC|newest]

Thread overview: 36+ 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     ` 廖亨权 [this message]
2017-04-06  8:38       ` Christoph Hellwig
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

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=5a5f1f1.8f7d.15b4267e21e.Coremail.liaohengquan1986@163.com \
    --to=liaohengquan1986@163.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=keith.busch@intel.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.