All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ivan Djelic <ivan.djelic@parrot.com>
Cc: linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH v3] ARM: OMAP3: gpmc: add BCH ecc api and modes
Date: Tue, 8 May 2012 17:29:28 -0700	[thread overview]
Message-ID: <20120509002927.GF5088@atomide.com> (raw)
In-Reply-To: <1335442669-13474-1-git-send-email-ivan.djelic@parrot.com>

* Ivan Djelic <ivan.djelic@parrot.com> [120426 05:23]:
> Hello,
> 
> Here is version 3 of this patch after review from Tony Lindgren.
> This version adds a separate initialization function mostly to check CPU
> compatibility. This check cannot be done in gpmc_enable_hwecc_bch() (which
> is meant to be called from mtd function ecc.hwctl) because ecc.hwctl is
> not called before the first NAND read access, and it cannot return an error
> status.

Thanks applying into devel-gpmc branch.

Tony

  reply	other threads:[~2012-05-09  0:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 12:17 [PATCH v3] ARM: OMAP3: gpmc: add BCH ecc api and modes Ivan Djelic
2012-04-26 12:17 ` Ivan Djelic
2012-05-09  0:29 ` Tony Lindgren [this message]
2012-05-09  8:07   ` Ivan Djelic
2012-05-09  8:07     ` Ivan Djelic
2012-05-09  8:10   ` Ivan Djelic
2012-05-09  8:10     ` Ivan Djelic
2012-05-09 15:31     ` Tony Lindgren
2012-05-09 15:31       ` Tony Lindgren
2012-05-10  6:49       ` Mohammed, Afzal
2012-05-10 13:07       ` Artem Bityutskiy
2012-05-10 15:17         ` Ivan Djelic
2012-05-10 15:52           ` Artem Bityutskiy
2012-05-10 17:45             ` Ivan Djelic
2012-05-10 19:02               ` Tony Lindgren
2012-05-10 19:02                 ` Tony Lindgren
2012-05-11 15:38               ` Artem Bityutskiy
2012-05-11 15:50               ` Mohammed, Afzal

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=20120509002927.GF5088@atomide.com \
    --to=tony@atomide.com \
    --cc=ivan.djelic@parrot.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.