From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933248AbdKBJWr (ORCPT ); Thu, 2 Nov 2017 05:22:47 -0400 Received: from mout.kundenserver.de ([212.227.17.24]:54874 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752865AbdKBJWp (ORCPT ); Thu, 2 Nov 2017 05:22:45 -0400 From: Arnd Bergmann To: Russell King , Vladimir Murzin Cc: Arnd Bergmann , Nicolas Pitre , afzal mohammed , Laura Abbott , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH] ARM: NOMMU: work around maybe-uninitialized warning Date: Thu, 2 Nov 2017 10:21:21 +0100 Message-Id: <20171102092155.737712-1-arnd@arndb.de> X-Mailer: git-send-email 2.9.0 X-Provags-ID: V03:K0:vEHnGhx52Mm0p+89XAqgOvElWNANZWRAt2HPqhJyfWNyq4kDX43 wh7qfXvMhRnG0uWtlj/rOf1AN17iARevWKIFa0kKgHm6U1EriXdKC+rkzkbXiL1kFVlUOuF Lb6BUxkJVAXQbv7ZYNZ6Ho/e62mf5sMoLgvTMSuvcsp5OQ1TG4EdmX2xt9gHokht/Zb30nq PbNbEWpXMSAjZF2UpvNzw== X-UI-Out-Filterresults: notjunk:1;V01:K0:EiramRrOe1A=:lSIx/lGRONQQBeuiLZnpJk 4vLEX39zlQdtuEJy2FAIImdU9fN0KgOljbF0HsSuGnj/9f9gSI3tvk9UCEpWkD1yKRdrR9pW9 H4oxAc4A5aNL6EeFOyL6b2IF0lu5UAdhGie4IJSduVzO76amg8VKrBQ2KAJZOVRtMEHTC/lns DRvFYRMU/uwq/x61MGNbwlKF/SX5cCxd6otFm80SJRs0prGGZ08VI0Y7+DfsHtXBqIi/yTrzw 3W4vPccEWhlCvy7V0/G8NTTwkfCXvoKuhImpu+GXSi7W8e1yuCII8xuRMHKkCD1fl5JAQ1qEW Tu6jIaLOsUVQssh12Ql0Xen3h26ICeBkGa4NHRtC/AOOPXtcQxqDYSLize8vc5GD2sbY9ouZ0 f1C3hecdHTvfcDRjhOP6JQniKUxaJQY/4gU4SI6VF3rLcUW4p3RlEYLZrtOl6cJKxA5VO+DB6 v8j60WHDsunsUUTp9KTvMegwL3dAd4Ku0L4lMLoXVZll4hBSQi2vLf0vHbo4Cnkab1LcGp9IC T//MuiuJSFnsv/IwBeb+Y4+hZUoe9VrHGdGtLJ1VFrJXXg/rsXfNT9nnLghb4+3TV+PxhHs27 hfcz72ZEl7yKovvli0/RL3Yb7Ns/OjlT1BnCOpRLDqMSVSAZXAHvQkJgLbyJHP78P6uDLN6ia bSIsfJZdyjjJkptOTryNZkHbhiJUyMPFYaYFPCrWk0D/iVetzvYMd/bokjLHCLl4+Qi7/ug5e QoxqLpdcRL+OmFCnKICzjQtgucOErPKiL7nWiw== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The reworked MPU code produces a new warning in some configurations, presumably starting with the code move after the compiler now makes different inlining decisions: arch/arm/mm/pmsa-v7.c: In function 'adjust_lowmem_bounds_mpu': arch/arm/mm/pmsa-v7.c:310:5: error: 'specified_mem_size' may be used uninitialized in this function [-Werror=maybe-uninitialized] This appears to be harmless, as we know that there is always at least one memblock, and the only way this could get triggered is if the for_each_memblock() loop was never entered. I could not come up with a better workaround than initializing the specified_mem_size to zero, but at least that is the value that the variable would have in the hypothetical case of no memblocks. Fixes: 877ec119dbbf ("ARM: 8706/1: NOMMU: Move out MPU setup in separate module") Signed-off-by: Arnd Bergmann --- Vladimir, if this looks good to you, can you forward it to Russell's patch tracker, or otherwise suggest a different fix? --- arch/arm/mm/pmsa-v7.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/mm/pmsa-v7.c b/arch/arm/mm/pmsa-v7.c index 106ae1c435a3..976df60ac426 100644 --- a/arch/arm/mm/pmsa-v7.c +++ b/arch/arm/mm/pmsa-v7.c @@ -234,7 +234,7 @@ static int __init allocate_region(phys_addr_t base, phys_addr_t size, /* MPU initialisation functions */ void __init adjust_lowmem_bounds_mpu(void) { - phys_addr_t specified_mem_size, total_mem_size = 0; + phys_addr_t specified_mem_size = 0, total_mem_size = 0; struct memblock_region *reg; bool first = true; phys_addr_t mem_start; -- 2.9.0