Re: [PATCH 1/1] ubi: Introduce block devices for UBI volumes

[Ezequiel Garcia <ezequiel.garcia@free-electrons.com>]

On Tue, Feb 11, 2014 at 10:05:33AM +0100, Willy Tarreau wrote:
> On Tue, Feb 11, 2014 at 09:37:25AM +0100, Geert Uytterhoeven wrote:
> > On Mon, Feb 10, 2014 at 10:43 PM, Willy Tarreau <w@1wt.eu> wrote:
> > > On Mon, Feb 10, 2014 at 10:39:18PM +0100, Piergiorgio Beruto wrote:
> > >> Hi all,
> > >> Please, the possibility to disable at compile time unneeded code to save
> > >> memory and/or cpu speed would make the life of embedded developers much more
> > >> easier.
> > >>
> > >> Ubiblk was exactly what we were looking for, in my personal opinion the
> > >> possibility to disable caching and rw feature is of very high value.
> > >
> > > Reminds me the happy days of CONFIG_TINY :-)
> > > So in practice it's probably just a matter of turning the options to :
> > >
> > >     Disable Caching (default N, say Y to save memory)
> > >     Disable Write support (default N, say Y to reduce code size)
> > 
> > But then allmodconfig builds will not exercise those code paths.
> > 
> > Don't you want:
> > 
> >     bool "Enable Caching" if !EXPERT
> >     default y
> > 
> >     bool "Enable Write support" if !EXPERT
> >     default y
> > 
> > ?
> 
> Sounds like an excellent idea!
> 

FWIW, we can also use CONFIG_EMBEDDED. However, most distros seem to
enable this by default.

Artem: What do you say about Geert's suggestion?
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com