linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: <dedekind1@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Ezequiel Garcia <elezegarcia@gmail.com>,
	Mike Frysinger <vapier@gentoo.org>,
	"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>
Subject: Re: [RFC/PATCH v2] ubi: Add ubiblock read-write driver
Date: Fri, 19 Apr 2013 10:05:19 -0700	[thread overview]
Message-ID: <5171794F.8000501@am.sony.com> (raw)
In-Reply-To: <1366374673.29520.125.camel@sauron.fi.intel.com>

On 04/19/2013 05:31 AM, Artem Bityutskiy wrote:
> 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 shows that this feature is not really needed, while adds
> maintenance burden.

Whoa there!  Just because it doesn't look like people are using fastmap
right now, don't think it won't get used in the future.   Really,
the people interested in fastmap are AFAIK mostly TV vendors, who are
just now migrating to 3.0 or 3.4 kernels.  I can assure you that fastmap
will get more attention when the major CE companies move to more
recent kernels (probably in about 1 to 2 years).

Likely, anyone who needs fastmap today has backported it, or plans
to backport it to their current product-facing kernel.  Unfortunately,
that means that bug reports and fixes usually don't show up on
public e-mail lists (due to version gap).

Richard (/Linutronix) was hired to do this work by the CE Workgroup.
If money is needed to get fastmap bugfixes and maintenance on his
priority list, please let us know and maybe we can do something.
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
=============================

  parent reply	other threads:[~2013-04-19 17:01 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
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 [this message]
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=5171794F.8000501@am.sony.com \
    --to=tim.bird@am.sony.com \
    --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=vapier@gentoo.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;
as well as URLs for NNTP newsgroup(s).