From: Keith Busch <keith.busch@intel.com>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: axboe@fb.com, jonathan.derrick@intel.com,
jay.e.sternberg@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] nvme:Fix error handling in the function nvme_init_integrity
Date: Tue, 29 Dec 2015 18:14:18 +0000 [thread overview]
Message-ID: <20151229181418.GA17092@localhost.localdomain> (raw)
In-Reply-To: <1451412648-21042-1-git-send-email-xerofoify@gmail.com>
On Tue, Dec 29, 2015 at 01:10:48PM -0500, Nicholas Krause wrote:
> - blk_integrity_register(ns->disk, &integrity);
> + if (blk_integrity_register(ns->disk, &integrity)) {
Nak; blk_integrity_register returns 'void'.
parent reply other threads:[~2015-12-29 18:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1451412648-21042-1-git-send-email-xerofoify@gmail.com>]
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=20151229181418.GA17092@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=axboe@fb.com \
--cc=jay.e.sternberg@intel.com \
--cc=jonathan.derrick@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xerofoify@gmail.com \
/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