All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Guilherme de Oliveira Costa <guilherme.oliveira@autotrac.com.br>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Filesystems over UBI can't handle badblocks
Date: Fri, 26 Feb 2016 10:24:53 +0200	[thread overview]
Message-ID: <1456475093.8024.14.camel@gmail.com> (raw)
In-Reply-To: <CAFLxGvwmRSHG1r9CAKa+1q-H2AWtZpS_Lgj2VTRcJfNZCG8JDw@mail.gmail.com>

On Thu, 2016-02-25 at 22:10 +0100, Richard Weinberger wrote:
> On Thu, Feb 25, 2016 at 11:49 AM, Artem Bityutskiy <dedekind1@gmail.c
> om> wrote:
> > 
> > Now, how to do it via UBI? I think this is not supported, but it
> > can be
> > implemented, I believe.
> Implementing this is rather easy.

I agree.

>  But what exactly is the use case?

I guess the reporter would come up with a good justification.

I can imagine one, but it is not very strong: you have a development
device, you mess with bad blocks by marking/unmarking them for some
research reasons. You put UBI image there, then remember that some of
the blocks were bad and want to mark them as bad without re-flashing
UBI. Kind of a developer convenience.

  reply	other threads:[~2016-02-26  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 20:08 Filesystems over UBI can't handle badblocks Guilherme de Oliveira Costa
2016-02-24 21:30 ` Richard Weinberger
2016-02-25  9:02   ` Ricard Wanderlof
2016-02-25 10:49 ` Artem Bityutskiy
2016-02-25 21:10   ` Richard Weinberger
2016-02-26  8:24     ` Artem Bityutskiy [this message]
     [not found] <7F9DB42F7DDA544EA3EB31D694929A30EB9762@PERU.autotrac.corp>
2016-02-29 19:06 ` Richard Weinberger

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=1456475093.8024.14.camel@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=guilherme.oliveira@autotrac.com.br \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.