Date: Wed, 3 Oct 2012 10:36:25 +0200
From: Richard Weinberger <richard@nod.at>
To: artem.bityutskiy@linux.intel.com
Cc: linux-mtd@lists.infradead.org, Heinz.Egger@linutronix.de,
        tglx@linutronix.de, linux-kernel@vger.kernel.org, tim.bird@am.sony.com
Subject: Re: UBI: Fastmap request for inclusion (v19)
Message-ID: <20121003103625.0bbff63c@spider.haslach.nod.at>
In-Reply-To: <1349252745.2017.120.camel@sauron.fi.intel.com>
References: <1348674710-102885-1-git-send-email-richard@nod.at>
	<1349252745.2017.120.camel@sauron.fi.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1194
Lines: 27

Am Wed, 03 Oct 2012 11:25:45 +0300
schrieb Artem Bityutskiy <artem.bityutskiy@linux.intel.com>:

> On Wed, 2012-09-26 at 17:51 +0200, Richard Weinberger wrote:
> > UBI Fastmap is an optional feature which stores the physical to
> > logical eraseblock relations in a checkpoint (called fastmap) to
> > reduce the initialization time of UBI. The current init time of UBI
> > is proportional to the number of physical erase blocks on the FLASH
> > device. With fastmap enabled the scan time is limited to a fixed
> > number of blocks.
> 
> Aiaiai complains and linux-next build fails :-( Last time I forgot to
> enable the fastmap kbuild option so aiaiai checked with that option
> disabled. Now I enabled it with a simple hack (default n -> default y)
> and here are aiaiai's complaints - there is a build failure for
> ARCH=i386.

Build fix for linux-next is on the way into your inbox.
I'm currently looking at the aiaiai output.

Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/