mm/memblock.c: remove redundant assignment to variable max_addr

The variable max_addr is being initialized with a value that is never read
and it is being updated later with a new value.  The initialization is
redundant and can be removed.

Signed-off-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
Link: http://lkml.kernel.org/r/20200228235003.112718-1-colin.king@canonical.com
Addresses-Coverity: ("Unused value")
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Colin Ian King 2020-04-01 21:11:01 -07:00 committed by Linus Torvalds
parent aa9f7d5172
commit 49aef7175c
1 changed files with 1 additions and 1 deletions

View File

@ -1698,7 +1698,7 @@ static phys_addr_t __init_memblock __find_max_addr(phys_addr_t limit)
void __init memblock_enforce_memory_limit(phys_addr_t limit) void __init memblock_enforce_memory_limit(phys_addr_t limit)
{ {
phys_addr_t max_addr = PHYS_ADDR_MAX; phys_addr_t max_addr;
if (!limit) if (!limit)
return; return;