From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [PATCH 1/3] mtd: nand: add NAND_NEED_SCRAMBLING option flag
Date: Fri, 16 Oct 2015 08:38:16 +0200 [thread overview]
Message-ID: <20151016083816.6e212acf@bbrezillon> (raw)
In-Reply-To: <20151016082854.24e076c2@bbrezillon>
On Fri, 16 Oct 2015 08:28:54 +0200
Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
> Hi Julian,
>
> On Fri, 16 Oct 2015 09:32:38 +1100
> Julian Calaby <julian.calaby@gmail.com> wrote:
>
> > Hi Boris,
> >
> > On Fri, Oct 16, 2015 at 4:17 AM, Boris Brezillon
> > <boris.brezillon@free-electrons.com> wrote:
> > > Some MLC NANDs are sensible to repeated patterns and require data to be
> >
> > Do you mean "sensitive" instead of "sensible"?
>
> Yes (I always mix the too, sensible is the french word for
two
> sensitive ;-)), I'll fix that.
>
> Best Regards,
>
> Boris
>
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-16 6:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 17:17 [PATCH 0/3] mtd: nand: add preliminary support for data scramblers Boris Brezillon
2015-10-15 17:17 ` [PATCH 1/3] mtd: nand: add NAND_NEED_SCRAMBLING option flag Boris Brezillon
2015-10-15 22:32 ` [linux-sunxi] " Julian Calaby
2015-10-16 6:28 ` Boris Brezillon
2015-10-16 6:38 ` Boris Brezillon [this message]
2015-10-15 17:17 ` [PATCH 2/3] mtd: nand: add NAND_NEED_SCRAMBLING flag to the H27UCG8T2ATR-BC definition Boris Brezillon
2015-10-20 7:20 ` Richard Weinberger
2015-10-20 9:15 ` Boris Brezillon
2015-10-15 17:17 ` [PATCH 3/3] mtd: nand: sunxi: add randomizer support Boris Brezillon
2015-10-15 22:33 ` [linux-sunxi] " Julian Calaby
2015-10-16 10:16 ` Boris Brezillon
2015-10-20 18:56 ` Richard Weinberger
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=20151016083816.6e212acf@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).