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] [PATCH] mtd: nand: revive "nand scrub" command
Date: Thu, 11 Dec 2014 15:43:11 -0600	[thread overview]
Message-ID: <1418334191.5581.58.camel@freescale.com> (raw)
In-Reply-To: <201412112237.33648.marex@denx.de>

On Thu, 2014-12-11 at 22:37 +0100, Marek Vasut wrote:
> On Thursday, December 11, 2014 at 09:37:10 PM, Scott Wood wrote:
> > On Thu, 2014-12-11 at 19:49 +0900, Masahiro Yamada wrote:
> > > Since commit ff94bc40af34 (mtd, ubi, ubifs: resync with Linux-3.14),
> > > the "nand scrub" command has not been working.
> > > 
> > > The scrub is a U-Boot extension and we have to modify nand_base.c
> > > that originates in Linux.
> > > 
> > > Mark the code with #ifdef __UBOOT__ so we will never accidentally
> > > drop it when we re-sync the NAND framework with Linux in the future.
> > 
> > No more "#ifdef __UBOOT__" please.
> 
> Do you happen to have a helpful suggestion how to clearly mark those bits of 
> code then please ?

This was already discussed. :-)

See the archives for why I think this is bad.

> > Instead, never again do a "start
> > from scratch" resync the way that the above commit was done.
> 
> This was already discussed, no need to revive this topic here now.

Sorry, but these patches fixing breakages that resulted from that merge
demonstrate that there is a need to revive it, if there's anyone that
still thinks it's a good idea -- Heiko seemed to be in agreement that
there's no need to do that for future syncs:
http://lists.denx.de/pipermail/u-boot/2014-November/194256.html

-Scott

  reply	other threads:[~2014-12-11 21:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 10:49 [U-Boot] [PATCH] mtd: nand: revive "nand scrub" command Masahiro Yamada
2014-12-11 20:37 ` Scott Wood
2014-12-11 21:37   ` Marek Vasut
2014-12-11 21:43     ` Scott Wood [this message]
2014-12-12  6:19       ` Heiko Schocher
2014-12-15 10:54         ` Masahiro Yamada
2014-12-15 11:13           ` Marek Vasut
2014-12-15 23:08             ` Scott Wood
2014-12-16  1:26               ` Tom Rini
2014-12-16  6:21                 ` Heiko Schocher
2014-12-16  6:24                   ` Scott Wood
2014-12-16  6:39                     ` Heiko Schocher
2014-12-16  6:41                     ` Masahiro Yamada

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=1418334191.5581.58.camel@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.