public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nand: reinstate lazy bad block scanning
Date: Wed, 05 Nov 2014 14:52:59 +0100	[thread overview]
Message-ID: <545A2BBB.10905@denx.de> (raw)
In-Reply-To: <1415050949.23458.268.camel@snotra.buserror.net>

Hello Scott, Rostislav,

Am 03.11.2014 22:42, schrieb Scott Wood:
> On Wed, 2014-10-22 at 13:40 +0200, Rostislav Lisovy wrote:
>> Commit ff94bc40af3481d47546595ba73c136de6af6929
>> ("mtd, ubi, ubifs: resync with Linux-3.14")
>> accidentally reverted part of the commit
>> 13f0fd94e3cae6f8a0d9fba5d367e311edc8ebde
>> ("NAND: Scan bad blocks lazily.").
>>
>> Reinstate the change as by commit
>> fb49454b1b6c7c6e238ac3c0b1e302e73eb1a1ea
>> ("nand: reinstate lazy bad block scanning")
>>
>> Signed-off-by: Rostislav Lisovy<lisovy@merica.cz>
>> ---
>>   drivers/mtd/nand/nand_base.c | 10 +++++++---
>>   1 file changed, 7 insertions(+), 3 deletions(-)
>
> Thanks for catching this.

Yep! I tested it on the siemens am335x boards so

Acked-by: Heiko Schocher <hs@denx.de>

> Heiko, this is the sort of thing I was concerned about with the "resync
> from scratch" approach.

I know, but the rebase was also error prone (at least in my attempts ...)

As we have now a clear defined base, maybe a resync with the help from
git works now in future?

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  parent reply	other threads:[~2014-11-05 13:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 11:40 [U-Boot] [PATCH] nand: reinstate lazy bad block scanning Rostislav Lisovy
2014-11-03 21:42 ` Scott Wood
2014-11-05  3:40   ` Masahiro Yamada
2014-11-05  5:49     ` Scott Wood
2014-11-05  8:01       ` Masahiro Yamada
2014-11-05 13:52   ` Heiko Schocher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-20 20:56 Scott Wood
2012-02-21  6:44 ` Heiko Schocher

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=545A2BBB.10905@denx.de \
    --to=hs@denx.de \
    --cc=u-boot@lists.denx.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