From: Brian Norris <computersforpeace@gmail.com>
To: linux-mtd@lists.infradead.org
Cc: Roland Stigge <stigge@antcom.de>
Subject: Re: [PATCH] mtd: lpc32xx: drop bitflip_threshold initialization
Date: Wed, 2 Jul 2014 17:25:01 -0700 [thread overview]
Message-ID: <20140703002501.GN3599@ld-irv-0074> (raw)
In-Reply-To: <1401267145-18218-1-git-send-email-computersforpeace@gmail.com>
On Wed, May 28, 2014 at 01:52:25AM -0700, Brian Norris wrote:
> These drivers don't need to explicitly initialize their bitflip
> thresholds. The comment is no longer correct, since nand_scan_tail()
> performs this initialization as of the following commit:
>
> commit ea3b2ea24ef0f2ef9c6795b19cff456195b6728a
> Author: Shmulik Ladkani <shmulik@jungo.com>
> Date: Fri Jun 8 18:29:06 2012 +0300
>
> mtd: nand: initialize bitflip_threshold prior to BBT scanning
>
> (It seems there were some parallel efforts on writing/submitting these
> drivers, and Shmulik's bug fix.)
>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> Cc: Roland Stigge <stigge@antcom.de>
Pushed to l2-mtd.git.
Brian
prev parent reply other threads:[~2014-07-03 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 8:52 [PATCH] mtd: lpc32xx: drop bitflip_threshold initialization Brian Norris
2014-07-03 0:25 ` Brian Norris [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=20140703002501.GN3599@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=stigge@antcom.de \
/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