All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] nand: current mainline show "new" startup output
Date: Tue, 14 Feb 2012 11:12:09 -0600	[thread overview]
Message-ID: <4F3A95E9.7060200@freescale.com> (raw)
In-Reply-To: <4F3A0164.9070204@denx.de>

On 02/14/2012 12:38 AM, Heiko Schocher wrote:
> Hello Scott,
> 
> Scott Wood wrote:
>> The problem isn't (just) the prints, which have always been there, but
>> when we do the scanning.  I suspect this patch accidentally reversed a
>> U-Boot local change to defer bad block scanning to first use.
> 
> Yes, seems so. So there are two points to decide:
> 
> - Do we need this prints? I vote for moving them to debug output

That's fine, but not related to this patch.

> - Do we move scanning back to first use? I vote for moving to "first use"

Yes, this is a regression introduced by this patch and should be fixed.

-Scott

      reply	other threads:[~2012-02-14 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  8:18 [U-Boot] nand: current mainline show "new" startup output Heiko Schocher
2012-02-13 17:06 ` Scott Wood
2012-02-14  6:38   ` Heiko Schocher
2012-02-14 17:12     ` Scott Wood [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=4F3A95E9.7060200@freescale.com \
    --to=scottwood@freescale.com \
    --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 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.