From: Christoph Hellwig <hch@lst.de>
To: "Nicholas A. Bellinger" <nab@daterainc.com>
Cc: linux-nvme <linux-nvme@lists.infradead.org>,
target-devel <target-devel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Nicholas Bellinger <nab@linux-iscsi.org>,
Keith Busch <keith.busch@intel.com>,
Jay Freyensee <james.p.freyensee@intel.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Sagi Grimberg <sagig@grimberg.me>, Christoph Hellwig <hch@lst.de>,
Jens Axboe <axboe@fb.com>
Subject: Re: [PATCH] nvme/host: Add missing blk_integrity tag_size + flags assignments
Date: Sun, 10 Apr 2016 16:59:30 +0200 [thread overview]
Message-ID: <20160410145930.GA21909@lst.de> (raw)
In-Reply-To: <1460171082-7212-1-git-send-email-nab@daterainc.com>
Does NVMe really force ATO=1? Sorry, didn't have much time to spend
with that part of the spec.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme/host: Add missing blk_integrity tag_size + flags assignments
Date: Sun, 10 Apr 2016 16:59:30 +0200 [thread overview]
Message-ID: <20160410145930.GA21909@lst.de> (raw)
In-Reply-To: <1460171082-7212-1-git-send-email-nab@daterainc.com>
Does NVMe really force ATO=1? Sorry, didn't have much time to spend
with that part of the spec.
next prev parent reply other threads:[~2016-04-10 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 3:04 [PATCH] nvme/host: Add missing blk_integrity tag_size + flags assignments Nicholas A. Bellinger
2016-04-09 3:04 ` Nicholas A. Bellinger
2016-04-10 13:47 ` Sagi Grimberg
2016-04-10 13:47 ` Sagi Grimberg
2016-04-10 14:59 ` Christoph Hellwig [this message]
2016-04-10 14:59 ` Christoph Hellwig
2016-04-11 20:28 ` Martin K. Petersen
2016-04-11 20:28 ` Martin K. Petersen
2016-04-11 20:27 ` Martin K. Petersen
2016-04-11 20:27 ` Martin K. Petersen
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=20160410145930.GA21909@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=james.p.freyensee@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=nab@daterainc.com \
--cc=nab@linux-iscsi.org \
--cc=sagig@grimberg.me \
--cc=target-devel@vger.kernel.org \
/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.