Linux block layer
 help / color / mirror / Atom feed
From: "Matias Bjørling" <mb@lightnvm.io>
To: "Javier González" <jg@lightnvm.io>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Javier González" <javier@cnexlabs.com>
Subject: Re: [PATCH 3/3] lightnvm: Add CRC read error
Date: Mon, 30 Jan 2017 11:16:10 +0100	[thread overview]
Message-ID: <fe372dff-b191-0284-90c7-d93c91fc0620@lightnvm.io> (raw)
In-Reply-To: <1485431260-20268-3-git-send-email-javier@cnexlabs.com>

On 01/26/2017 12:47 PM, Javier González wrote:
> Let the host differentiate between a read error and a CRC check error on
> the device side.
> 
> Signed-off-by: Javier González <javier@cnexlabs.com>
> ---
>  include/linux/lightnvm.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/include/linux/lightnvm.h b/include/linux/lightnvm.h
> index 11c318e..51cda67 100644
> --- a/include/linux/lightnvm.h
> +++ b/include/linux/lightnvm.h
> @@ -108,6 +108,7 @@ enum {
>  	NVM_RSP_ERR_FAILWRITE	= 0x40ff,
>  	NVM_RSP_ERR_EMPTYPAGE	= 0x42ff,
>  	NVM_RSP_ERR_FAILECC	= 0x4281,
> +	NVM_RSP_ERR_FAILCRC	= 0x4004,
>  	NVM_RSP_WARN_HIGHECC	= 0x4700,
>  
>  	/* Device opcodes */
> 

Thanks. Applied.

  reply	other threads:[~2017-01-30 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 11:47 [PATCH 1/3] lightnvm: submit erases using the I/O path Javier González
2017-01-26 11:47 ` [PATCH 2/3] lightnvm: allow targets to use sysfs Javier González
2017-01-30 10:27   ` Matias Bjørling
2017-01-26 11:47 ` [PATCH 3/3] lightnvm: Add CRC read error Javier González
2017-01-30 10:16   ` Matias Bjørling [this message]
2017-01-30 11:31 ` [PATCH 1/3] lightnvm: submit erases using the I/O path Matias Bjørling

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=fe372dff-b191-0284-90c7-d93c91fc0620@lightnvm.io \
    --to=mb@lightnvm.io \
    --cc=javier@cnexlabs.com \
    --cc=jg@lightnvm.io \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox