On Saturday 03 January 2015 15:44:38 Aaro Koskinen wrote: > > On Sat, Jan 03, 2015 at 01:51:53PM +0100, Arnd Bergmann wrote: > > On Saturday 03 January 2015 07:21:49 Paul Walmsley wrote: > > > Another ~300KB kernel object size increase for omap2plus_defconfig > > > kernels. > > > > 300kb seems like a lot for a single release. Have you looked into > > where this is coming from? > > In 3.19-rc1, all initrd decompressors are by default enabled... > > CONFIG_RD_GZIP=y > -# CONFIG_RD_BZIP2 is not set > -# CONFIG_RD_LZMA is not set > -# CONFIG_RD_XZ is not set > -# CONFIG_RD_LZO is not set > -# CONFIG_RD_LZ4 is not set > +CONFIG_RD_BZIP2=y > +CONFIG_RD_LZMA=y > +CONFIG_RD_XZ=y > +CONFIG_RD_LZO=y > +CONFIG_RD_LZ4=y > Interesting, this seems to be the opposite of the intention of the change that caused it, which tried to let you disable the algorithms without selecting CONFIG_EXPERT. For some reason that is impossible to know now, they already defaulted to 'n' when EXPERT was set, but now they default to 'y'. Does this indeed cause the entire change in size? Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
