Messages in this thread | | | Date | Wed, 27 Aug 2014 13:53:48 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH 1/2] x86: use memblock_alloc_range() or memblock_alloc_base() |
| |
On Sun, 24 Aug 2014 23:56:02 +0900 Akinobu Mita <akinobu.mita@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()?
| |