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>,
	"Matias Bjørling" <matias@cnexlabs.com>
Subject: Re: [PATCH 2/3] lightnvm: rename scrambler controller hint
Date: Fri, 24 Feb 2017 18:08:12 +0100	[thread overview]
Message-ID: <d414955a-60cb-2d09-6731-2f42b792f3eb@lightnvm.io> (raw)
In-Reply-To: <1487952846-29476-2-git-send-email-javier@cnexlabs.com>

On 02/24/2017 05:14 PM, Javier González wrote:
> According to the OCSSD 1.2 specification, the 0x200 hint enables the
> media scrambler for the read/write opcode, providing that the controller
> has been correctly configured by the firmware. Rename the macro to
> represent this meaning.
>
> Signed-off-by: Javier González <javier@cnexlabs.com>
> Signed-off-by: Matias Bjørling <matias@cnexlabs.com>
> ---
>  include/linux/lightnvm.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/lightnvm.h b/include/linux/lightnvm.h
> index 6a3534b..bebea80 100644
> --- a/include/linux/lightnvm.h
> +++ b/include/linux/lightnvm.h
> @@ -123,7 +123,7 @@ enum {
>  	/* NAND Access Modes */
>  	NVM_IO_SUSPEND		= 0x80,
>  	NVM_IO_SLC_MODE		= 0x100,
> -	NVM_IO_SCRAMBLE_DISABLE	= 0x200,
> +	NVM_IO_SCRAMBLE_ENABLE	= 0x200,
>
>  	/* Block Types */
>  	NVM_BLK_T_FREE		= 0x0,
>

Thanks, applied for 4.12.

  reply	other threads:[~2017-02-24 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24 16:14 [PATCH 1/3] lightnvm: submit erases using the I/O path Javier González
2017-02-24 16:14 ` [PATCH 2/3] lightnvm: rename scrambler controller hint Javier González
2017-02-24 17:08   ` Matias Bjørling [this message]
2017-02-24 16:14 ` [PATCH 3/3] lightnvm: free reverse device map Javier González
2017-02-24 17:08   ` Matias Bjørling
2017-02-24 17:08 ` [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=d414955a-60cb-2d09-6731-2f42b792f3eb@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 \
    --cc=matias@cnexlabs.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