linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: dedekind1@gmail.com
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Ezequiel Garcia <elezegarcia@gmail.com>,
	"richard.weinberger@gmail.com" <richard.weinberger@gmail.com>,
	Michael Opdenacker <michael.opdenacker@free-electrons.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Gupta, Pekon" <pekon@ti.com>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	Tim Bird <tim.bird@am.sony.com>
Subject: Re: [RFC/PATCH v2] ubi: Add ubiblock read-write driver
Date: Fri, 19 Apr 2013 08:53:50 -0400	[thread overview]
Message-ID: <201304190853.54402.vapier@gentoo.org> (raw)
In-Reply-To: <1366374673.29520.125.camel@sauron.fi.intel.com>

[-- Attachment #1: Type: Text/Plain, Size: 1084 bytes --]

On Friday 19 April 2013 08:31:13 Artem Bityutskiy wrote:
> On Fri, 2013-04-19 at 07:57 -0400, Mike Frysinger wrote:
> > the reason we're talking about not allowing write support at the
> > *block* layer
> > is because it's questionable how many people actually want this, the
> > performance isn't good (compared to native flash filesystems), and
> > because the
> > write/wear characteristics are unknown.
> 
> My opinion that unless people demonstrate that they need this, e.g. in a
> product, etc, we should not merge this stuff.
> 
> We recently merged fastmap, which is a big chunk of code, and it looks
> like no one really needs it. There was a problem report, and Richard
> promised to look, but did not. I do not blame him, he is a busy guy. But
> this shoes that this feature is not really needed, while adds
> maintenance burden.
> 
> To put it differently, I do recommend to merge more UBI-related code
> without a solid user-base.

also to be clear, i plan on using UBI block in read-only mode, so i'd like to 
see an ubiblock driver merged
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-04-19 12:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 12:21 [RFC/PATCH v2] ubi: Add ubiblock read-write driver Ezequiel Garcia
2012-12-12 15:21 ` richard -rw- weinberger
2012-12-12 15:50   ` Gregory CLEMENT
2012-12-12 16:14     ` richard -rw- weinberger
2012-12-12 16:30       ` Greg KH
2012-12-12 16:32         ` richard -rw- weinberger
2012-12-12 16:18   ` Ezequiel Garcia
2012-12-12 16:35     ` Ezequiel Garcia
2012-12-12 17:26       ` Michael Opdenacker
2012-12-12 19:50         ` Tim Bird
2013-04-18 20:30 ` Mike Frysinger
2013-04-18 20:58   ` Peter Korsgaard
2013-04-19  0:13   ` Ezequiel Garcia
2013-04-19  1:28     ` Mike Frysinger
2013-04-19  7:10       ` Gupta, Pekon
2013-04-19 11:57         ` Mike Frysinger
2013-04-19 12:31           ` Artem Bityutskiy
2013-04-19 12:31             ` Bityutskiy, Artem
2013-04-19 12:53             ` Mike Frysinger [this message]
2013-04-19 12:55               ` Matthieu CASTET
2013-04-24 16:27                 ` Mike Frysinger
2013-04-19 12:56               ` Artem Bityutskiy
2013-04-19 15:02             ` Ezequiel Garcia
2013-04-19 17:05             ` Tim Bird
2013-04-20 18:12               ` Brian Norris
2013-05-13  7:44               ` Artem Bityutskiy
2013-04-20  7:50             ` richard -rw- weinberger
2013-05-13  7:49               ` Artem Bityutskiy
2013-05-13  9:23                 ` richard -rw- weinberger
2013-04-19 12:27       ` Ezequiel Garcia
2013-05-13  7:28   ` 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=201304190853.54402.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=dedekind1@gmail.com \
    --cc=elezegarcia@gmail.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael.opdenacker@free-electrons.com \
    --cc=pekon@ti.com \
    --cc=richard.weinberger@gmail.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=tim.bird@am.sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).