From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: move protection information check into nvme_setup_rw
Date: Thu, 15 Jun 2017 05:17:18 -0700 [thread overview]
Message-ID: <20170615121718.GB18698@infradead.org> (raw)
In-Reply-To: <d64302e7-6fae-3171-5634-59da3c964bee@grimberg.me>
On Thu, Jun 15, 2017@12:21:45PM +0300, Sagi Grimberg wrote:
> Not directly related to this patch, but 8 should be replaced with
> sizeof(struct t10_pi_tuple).
>
> Otherwise looks good,
>
> Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
>
> Should I send out an incremental change?
Yes, please do.
prev parent reply other threads:[~2017-06-15 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 16:36 [PATCH] nvme: move protection information check into nvme_setup_rw Christoph Hellwig
2017-06-13 8:00 ` Johannes Thumshirn
2017-06-13 8:03 ` Christoph Hellwig
2017-06-13 14:55 ` Keith Busch
2017-06-15 9:21 ` Sagi Grimberg
2017-06-15 12:11 ` Christoph Hellwig
2017-06-15 12:17 ` Christoph Hellwig [this message]
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=20170615121718.GB18698@infradead.org \
--to=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox