From: Wolfram Sang <w.sang@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: [PATCH] commands: add scrub
Date: Thu, 13 Dec 2012 16:46:39 +0100 [thread overview]
Message-ID: <20121213154639.GB2632@pengutronix.de> (raw)
In-Reply-To: <1355413554-16312-1-git-send-email-w.sang@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 516 bytes --]
On Thu, Dec 13, 2012 at 04:45:54PM +0100, Wolfram Sang wrote:
> Allows erasing a whole NAND device including the bad blocks. Only meant
> for development where one might accidently overwrite real bad block
> information.
>
> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Ooops, wrong one. Please discard until I post the whole series later.
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-12-13 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 15:45 Wolfram Sang
2012-12-13 15:46 ` Wolfram Sang [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=20121213154639.GB2632@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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