From: Artem Bityutskiy <dedekind@infradead.org>
To: Johan <kungjohan@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problem with ubiformat
Date: Fri, 16 Jan 2009 16:46:16 +0200 [thread overview]
Message-ID: <1232117176.25068.32.camel@localhost.localdomain> (raw)
In-Reply-To: <de9b121e0901160636l1d946e9bhaf5c269a5131ea7d@mail.gmail.com>
On Fri, 2009-01-16 at 15:36 +0100, Johan wrote:
> This is my output of flash_eraseall, so it looks like the same
> input/output error exist in flash_eraseall but it continues anyway.
Yeah, ubiformat should not panic as well. I think it should ask the user
whether to:
a) continue
b) stop
c) mark the eraseblock as bad and continue
Well, if the -f option is given, it should just continue.
I'll add this to my TODO list and will do later. But you may
easily implement this yorself and send a patch if you do not
want to wait.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-01-16 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 16:54 Problem with ubiformat Johan
2009-01-16 11:29 ` Artem Bityutskiy
2009-01-16 14:36 ` Johan
2009-01-16 14:46 ` Artem Bityutskiy [this message]
2009-03-26 12:39 ` Artem Bityutskiy
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=1232117176.25068.32.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=kungjohan@gmail.com \
--cc=linux-mtd@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