From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
To: "Philip, Avinash" <avinashphilip@ti.com>
Cc: dwmw2@infradead.org, afzal@ti.com, tony@atomide.com,
broonie@opensource.wolfsonmicro.com, rmk+kernel@arm.linux.org.uk,
gregkh@linuxfoundation.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
nsekhar@ti.com, gururaja.hebbar@ti.com, ivan.djelic@parrot.com
Subject: Re: [PATCH v2 0/3] mtd: nand: OMAP: ELM error correction support for BCH ecc
Date: Thu, 15 Nov 2012 13:22:14 +0200 [thread overview]
Message-ID: <1352978534.2221.33.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1351667307-447-1-git-send-email-avinashphilip@ti.com>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On Wed, 2012-10-31 at 12:38 +0530, Philip, Avinash wrote:
> Support to use ELM as BCH 4 & 8 bit error correction module. Also performance
> enhancement by adding single shot read_page and write_page functions for the
> nand flashes with page size less than 4 KB.
>
> ELM module can be used to correct errors reported by BCH 4, 8 & 16 bit
> ECC scheme. For now only 4 & 8 bit support is added.
>
> BCH 4 & 8 bit error detection support is already available in mainline
> kernel and works with software error correction.
>
> This series is based on [1] and tested with RFC: OMAP GPMC bindings
> patch series
>
> 1. linux-next/20121030
Would you please re-send a version which cleanly applies to the
l2-mtd.git tree? This series has many conflicts. Thanks!
git://git.infradead.org/users/dedekind/l2-mtd.git
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-15 11:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 7:08 [PATCH v2 0/3] mtd: nand: OMAP: ELM error correction support for BCH ecc Philip, Avinash
2012-10-31 7:08 ` [PATCH v2 1/3] mtd: nand: omap2: Update nerrors using ecc.strength Philip, Avinash
2012-10-31 7:08 ` [PATCH v2 2/3] mtd: devices: elm: Add support for ELM error correction Philip, Avinash
2012-10-31 7:08 ` [PATCH v2 3/3] mtd: nand: omap2: Support for hardware BCH " Philip, Avinash
2012-11-30 12:28 ` Artem Bityutskiy
2012-12-04 13:16 ` Philip, Avinash
2012-11-15 11:22 ` Artem Bityutskiy [this message]
2012-11-19 12:44 ` [PATCH v2 0/3] mtd: nand: OMAP: ELM error correction support for BCH ecc Philip, Avinash
2012-11-21 7:01 ` Philip, Avinash
[not found] ` <518397C60809E147AF5323E0420B992E3E9EC70D-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-11-22 10:43 ` Artem Bityutskiy
[not found] ` <1353581032.2701.34.camel-Bxnoe/o8FG+Ef9UqXRslZEEOCMrvLtNR@public.gmane.org>
2012-11-22 14:37 ` Philip, Avinash
2012-11-30 12:28 ` Artem Bityutskiy
2012-12-04 13:20 ` Philip, Avinash
2012-11-27 9:07 ` Philip, Avinash
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=1352978534.2221.33.camel@sauron.fi.intel.com \
--to=artem.bityutskiy@linux.intel.com \
--cc=afzal@ti.com \
--cc=avinashphilip@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=gururaja.hebbar@ti.com \
--cc=ivan.djelic@parrot.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nsekhar@ti.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).