Prev: [PATCH 30/49] memblock: Export MEMBLOCK_ERROR again
Next: [PATCH 48/49] x86, memblock: Use memblock_memory_size()/memblock_free_memory_size() to get correct dma_reserve
From: Yinghai Lu on 6 Jul 2010 18:50
all callees assume it return MEMBLOCK_ERROR when it fail to find a range

Signed-off-by: Yinghai Lu <yinghai(a)kernel.org>
---
mm/memblock.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/mm/memblock.c b/mm/memblock.c
index c71b847..8ed7901 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -154,7 +154,7 @@ static phys_addr_t __init memblock_find_base(phys_addr_t size, phys_addr_t align
if (found != MEMBLOCK_ERROR)
return found;
}
- return 0;
+ return MEMBLOCK_ERROR;
}

static void memblock_remove_region(struct memblock_type *type, unsigned long r)
--
1.6.4.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 30/49] memblock: Export MEMBLOCK_ERROR again
Next: [PATCH 48/49] x86, memblock: Use memblock_memory_size()/memblock_free_memory_size() to get correct dma_reserve