From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd: nand: revive "nand scrub" command
Date: Tue, 16 Dec 2014 00:24:06 -0600 [thread overview]
Message-ID: <1418711046.5581.90.camel@freescale.com> (raw)
In-Reply-To: <548FCF5F.9020809@denx.de>
On Tue, 2014-12-16 at 07:21 +0100, Heiko Schocher wrote:
> Hello Tom, Scott,
>
> Am 16.12.2014 02:26, schrieb Tom Rini:
> > As we're neck deep in "See? Scott was right" I'm inclined to go with
> > what Scott is saying. We tried it, it actively didn't work, lets step
> > back, evaluate and move along.
>
> Ok, I have no objections against that, it was just my point of view ...
>
> And yes, I missed here and there some pieces when syncing with
> linux 3.14 ... sorry for that, but I could not test every scenario for
> every board ... and we had no clean base for using git, which at last
> in my attempt ended in a big mess when syncing with linux ... so I started
> more or less from scratch ...
I understand that for some of the mtd parts, but the nand code did have
a relatively clean base.
> So ...
>
> Who will send a "delete ifdef" patch?
I will.
> Who will test, how a resync with linux (saying 3.17 ?) work now with git?
>
> If this test is done, we can decide, which way is the "way to go" ... ?
I'll try a 3.18 sync soon.
-Scott
next prev parent reply other threads:[~2014-12-16 6:24 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
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 [this message]
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=1418711046.5581.90.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox