From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd: nand: revive "nand scrub" command
Date: Thu, 11 Dec 2014 22:37:33 +0100 [thread overview]
Message-ID: <201412112237.33648.marex@denx.de> (raw)
In-Reply-To: <1418330230.5581.54.camel@freescale.com>
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 ?
> 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.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-12-11 21:37 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 [this message]
2014-12-11 21:43 ` Scott Wood
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=201412112237.33648.marex@denx.de \
--to=marex@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