From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jon Ringle <jon@ringle.org>
Cc: barebox@lists.infradead.org
Subject: Re: ubiformat
Date: Wed, 23 Mar 2011 09:49:10 +0100 [thread overview]
Message-ID: <20110323084910.GD29521@pengutronix.de> (raw)
In-Reply-To: <AANLkTimU4PFrcfHE+Ns8NO69akeD07tMnVFhdXAvkV5V@mail.gmail.com>
On Mon, Mar 21, 2011 at 02:39:51PM -0400, Jon Ringle wrote:
> I am starting work on creating a ubiformat function for barebox, but just
> wanted to first find out if there is already any work-in-progress for this
> functionality.
Not that I know of. I usually use regular erase commands which of course
erase the erasecounters aswell.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-03-23 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 18:39 ubiformat Jon Ringle
2011-03-23 8:49 ` Sascha Hauer [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=20110323084910.GD29521@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jon@ringle.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