devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Sierra <asierra@xes-inc.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	devicetree@vger.kernel.org, linux-mtd@lists.infradead.org,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	Jordan Friendshuh <jfriendshuh@xes-inc.com>
Subject: Re: [PATCH v2] mtd: fsl_upm: Support NAND ECC DTS properties
Date: Tue, 16 Dec 2014 20:11:12 -0600 (CST)	[thread overview]
Message-ID: <1857520613.113885.1418782272200.JavaMail.zimbra@xes-inc.com> (raw)
In-Reply-To: <20141217003506.GK9759@ld-irv-0074>

----- Original Message -----
> From: "Brian Norris" <computersforpeace@gmail.com>
> Sent: Tuesday, December 16, 2014 6:35:06 PM
> 
> Hi Aaron,
> 
> On Sat, Nov 08, 2014 at 01:11:56PM -0600, Aaron Sierra wrote:
> > From: Jordan Friendshuh <jfriendshuh@xes-inc.com>
> > 
> > Support the generic nand-ecc-mode and nand-ecc-strength device-tree
> > properties with the Freescale UPM NAND driver.
> > 
> > This patch preserves the default software ECC mode while adding the
> > ability to use BCH ECC for larger NAND devices.
> > 
> > Signed-off-by: Jordan Friendshuh <jfriendshuh@xes-inc.com>
> > Signed-off-by: Aaron Sierra <asierra@xes-inc.com>
> > ---
> > v2:
> >     * Now using ECC mode and strength helpers from of_mtd.h
> >     * ECC mode and strength checking is more robust
> 
> Should I be expecting an update? Ezequiel made a few comments, and I'm
> not sure if you were planning any action based on them.

Brian,

Yes, I intend to provide an updated patch based on Ezequiel's comments.
Sorry for not being clear about this earlier. I thought I would have
done the work by now.

-Aaron

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2014-12-17  2:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <71973089.5152.1415472776826.JavaMail.zimbra@xes-inc.com>
2014-11-08 19:11 ` [PATCH v2] mtd: fsl_upm: Support NAND ECC DTS properties Aaron Sierra
     [not found]   ` <1854666513.5578.1415473916534.JavaMail.zimbra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
2014-11-23  0:55     ` Ezequiel Garcia
2014-11-24 15:22       ` Aaron Sierra
2014-11-25 20:08     ` Ezequiel Garcia
     [not found]       ` <5474E1DB.1090207-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>
2014-11-25 22:19         ` Aaron Sierra
     [not found]           ` <412246484.206926.1416953948359.JavaMail.zimbra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
2014-11-25 22:42             ` Ezequiel Garcia
     [not found]               ` <547505E7.7000502-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>
2014-11-25 23:23                 ` Aaron Sierra
2014-12-17  0:35     ` Brian Norris
2014-12-17  2:11       ` Aaron Sierra [this message]

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=1857520613.113885.1418782272200.JavaMail.zimbra@xes-inc.com \
    --to=asierra@xes-inc.com \
    --cc=computersforpeace@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=jfriendshuh@xes-inc.com \
    --cc=linux-mtd@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).