Re: [PATCH 1/2] x86: use memblock_alloc_range() or memblock_alloc_base()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 24 Aug 2014 23:56:02 +0900 Akinobu Mita <akinobu.mita@xxxxxxxxx> 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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]