From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
Kamal Dasu <kdasu.kdev@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Frank Rowand <frowand.list@gmail.com>
Subject: Re: [PATCH V2 0/4] mtd: nand: add enum nand_ecc_algo
Date: Sat, 2 Apr 2016 09:11:56 +0200 [thread overview]
Message-ID: <20160402091156.00c01288@bbrezillon> (raw)
In-Reply-To: <20160330152710.0b33d28d@bbrezillon>
On Wed, 30 Mar 2016 15:27:10 +0200
Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
> Hi Rafal,
>
> On Wed, 23 Mar 2016 11:18:59 +0100
> Rafał Miłecki <zajec5@gmail.com> wrote:
>
> > Some time ago I started working on a new "nand-ecc-algo" property to allow
> > specifying ECC algorithm for hardware ECC mode as well.
> > Boris pointed out it's becoming a bit messy that way as we already have value
> > NAND_ECC_SOFT_BCH.
> > I suggested deprecating "soft_bch" value from nand-ecc-mode property and got
> > Boris agreed and no objections from others. So there is how I want to implement
> > this.
> > If you agree on this way & apply my patches, I'll start modifying NAND drivers
> > (similarly to the nandsim) and then will try to drop NAND_ECC_SOFT_BCH except
> > for handling backward compatibility.
> > Then finally we should be able to add "nand-ecc-algo" property support properly.
>
> Can you configure git-send-email to not encode your messages in base64?
Nevermind, my mailer was showing me base64 encoded content, but after a
reboot everything is back to normal. Don't know what happened exactly.
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-02 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 10:18 [PATCH V2 0/4] mtd: nand: add enum nand_ecc_algo Rafał Miłecki
2016-03-23 10:19 ` [PATCH V2 1/4] mtd: nand: add new enum for storing ECC algorithm Rafał Miłecki
2016-03-23 10:19 ` [PATCH V2 2/4] of: mtd: prepare helper reading NAND ECC algo from DT Rafał Miłecki
2016-03-23 10:19 ` [PATCH V2 3/4] mtd: nand: set ECC algorithm in nand_dt_init Rafał Miłecki
2016-03-23 10:19 ` [PATCH V2 4/4] mtd: nand: nandsim: set ECC algorithm explicitly Rafał Miłecki
2016-03-23 10:43 ` [PATCH V2 0/4] mtd: nand: add enum nand_ecc_algo Boris Brezillon
2016-03-30 13:27 ` Boris Brezillon
2016-04-02 7:11 ` Boris Brezillon [this message]
2016-03-30 13:58 ` Boris Brezillon
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=20160402091156.00c01288@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=grant.likely@linaro.org \
--cc=kdasu.kdev@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=zajec5@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