On Sun, 24 Aug 2014 23:56:02 +0900 Akinobu Mita <akinobu.m...@gmail.com> wrote:
> Replace memblock_find_in_range() and memblock_reserve() with > memblock_alloc_range() or memblock_alloc_base(). Please spend a little more time preparing the changelogs? Why are we making this change? Because memblock_alloc_range() is equivalent to memblock_find_in_range()+memblock_reserve() and it's just a cleanup? Or is there some deeper functional reason? Does memblock_find_in_range() need to exist? Can we convert all callers to memblock_alloc_range()? -- 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/
