On Mon, 13 Jan 2014 09:27:44 -0500 Santosh Shilimkar <santosh.shilim...@ti.com> wrote:
> > It seems to me to be absolutely silly to have code introduce a warning > > yet push the fix for the warning via a completely different tree... > > > I mixed it up. Sorry. Some how I thought there was some other build > configuration thrown the same warning with memblock series and hence > suggested the patch to go via Andrew's tree. Yes, I too had assumed that the warning was caused by the bootmem patches in -mm. But it in fact occurs in Linus's current tree. I'll drop mm-arm-fix-arms-__ffs-to-conform-to-avoid-warning-with-no_bootmem.patch and I'll assume that rmk will fix this up at an appropriate time. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
