From: David Woodhouse <dwmw2@infradead.org>
To: dedekind@infradead.org
Cc: Andrew Morton <akpm@osdl.org>,
tglx@linutronix.de, haver@vnet.ibm.com,
Josh Boyer <jwboyer@linux.vnet.ibm.com>,
arnez@vnet.ibm.com, linux-mtd@mgw-ext13.nokia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UBI
Date: Wed, 29 Nov 2006 17:12:23 +0000 [thread overview]
Message-ID: <1164820343.14595.104.camel@pmac.infradead.org> (raw)
In-Reply-To: <1164819769.576.53.camel@sauron>
On Wed, 2006-11-29 at 19:02 +0200, Artem Bityutskiy wrote:
> Hello Andrew,
>
> we have announced UBI several months ago in the MTD mailing list. It was
> successfully used in our setup and we've got positive feedback.
>
> In short, it is kind of LVM layer but for flash (MTD) devices which
> hides flash devices complexities like bad eraseblocks (on NANDs) and
> wear. The documentation is available at the MTD web site:
> http://www.linux-mtd.infradead.org/doc/ubi.html
> http://www.linux-mtd.infradead.org/faq/ubi.html
>
> The source code is available at the UBI GIT tree:
> git://git.infradead.org/home/dedekind/ubi-2.6.git
Make that git://git.infradead.org/~dedekind/ubi-2.6.git
or http://git.infradead.org/?p=users/dedekind/ubi-2.6.git
And it would be helpful (at least to me) if you'd keep an 'mtd' or
'linus' branch in your tree, which shows the point at which you last
pulled from your upstream tree(s). That way, 'git-diff mtd..' or
'gitk mtd..' work.
--
dwmw2
prev parent reply other threads:[~2006-11-29 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 17:02 Artem Bityutskiy
2006-11-29 17:12 ` David Woodhouse [this message]
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=1164820343.14595.104.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=arnez@vnet.ibm.com \
--cc=dedekind@infradead.org \
--cc=haver@vnet.ibm.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@mgw-ext13.nokia.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®