[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM9Jb+jrC0C0RGV+uM_bs5QMSFaYPHjqzOo8vQZ+y-WghQtVvg@mail.gmail.com>
Date: Sat, 29 Feb 2020 08:47:16 +0100
From: Pankaj Gupta <pankaj.gupta.linux@...il.com>
To: Colin King <colin.king@...onical.com>
Cc: Mike Rapoport <rppt@...ux.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/memblock: remove redundant assignment to variable max_addr
>
> From: Colin Ian King <colin.king@...onical.com>
>
> 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.
>
> Addresses-Coverity: ("Unused value")
> Signed-off-by: Colin Ian King <colin.king@...onical.com>
> ---
> mm/memblock.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/memblock.c b/mm/memblock.c
> index eba94ee3de0b..4d06bbaded0f 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -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)
> {
> - phys_addr_t max_addr = PHYS_ADDR_MAX;
> + phys_addr_t max_addr;
>
> if (!limit)
> return;
> --
> 2.25.0
Reviewed-by: Pankaj Gupta <pankaj.gupta.linux@...il.com>
>
>
Powered by blists - more mailing lists