From: "Josh Boyer" <jwboyer@gmail.com>
To: linux-mtd <linux-mtd@lists.infradead.org>
Subject: State of UBI
Date: Sat, 9 Sep 2006 21:22:13 -0500 [thread overview]
Message-ID: <625fc13d0609091922m42a1caeagfa4e87bc18f2a8d6@mail.gmail.com> (raw)
Hi all,
Where are we with UBI? It seems Artem has been steadily committing
fixes to the ubi git tree. There's supposedly still interest from
other projects. Yet it hasn't been reviewed very much, for which I'm
partly to blame. So where should we go from here?
I think a good start would be to list what's missing. I know that it
needs a patch to allow double page writes on NAND. There's also the
missing JFFS2 integration, or rather two competing versions of it. Is
there anything else? Something documented in a TODO list would be
good.
Then there's a matter of when should it be merged. As it stands right
now, UBI is in limbo and I'd hate to see something with good potential
just sit around rotting. Having a merge goal would perhaps provide
some motivation. It could be a date or a kernel version, but it
should be realistic.
So lets come up with some kind of plan to get it reviewed, tested, and
merged. My hope would be that all involved so far, or even those that
want to help out, could reply with their thoughts. I'm afraid some
won't for various reasons. Perhaps if some of us are going to LCA we
could get together and hash some things out more in detail, but I'd
rather not wait until then to get things moving.
josh
next reply other threads:[~2006-09-10 2:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 2:22 Josh Boyer [this message]
2006-09-10 8:47 ` State of UBI dedekind
2006-09-10 10:52 ` David Woodhouse
2006-09-10 12:35 ` Josh Boyer
2006-09-10 13:19 ` dedekind
2006-09-10 17:00 ` dedekind
2006-09-10 17:44 ` David Woodhouse
2006-09-11 6:11 ` dedekind
2006-09-10 12:32 ` Josh Boyer
2006-09-10 13:34 ` dedekind
2006-09-10 14:11 ` Josh Boyer
2006-09-10 14:23 ` dedekind
2006-09-11 8:11 ` David Woodhouse
2006-09-11 9:19 ` dedekind
2006-09-11 13:21 ` Josh Boyer
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=625fc13d0609091922m42a1caeagfa4e87bc18f2a8d6@mail.gmail.com \
--to=jwboyer@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