[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <ADE657CA350FB648AAC2C43247A983F001F382220E0F@AUSP01VMBX24.collaborationhost.net>
Date: Tue, 14 Jun 2011 19:47:19 -0500
From: H Hartley Sweeten <hartleys@...ionengravers.com>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"benh@...nel.crashing.org" <benh@...nel.crashing.org>,
"yinghai@...nel.org" <yinghai@...nel.org>,
"hpa@...ux.intel.com" <hpa@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: [Q] mm/memblock.c: cast truncates bits from RED_INACTIVE
Hello all,
Sparse is reporting a couple warnings in mm/memblock.c:
warning: cast truncates bits from constant value (9f911029d74e35b becomes 9d74e35b)
The warnings are due to the cast of RED_INACTIVE in memblock_analyze():
/* Check marker in the unused last array entry */
WARN_ON(memblock_memory_init_regions[INIT_MEMBLOCK_REGIONS].base
!= (phys_addr_t)RED_INACTIVE);
WARN_ON(memblock_reserved_init_regions[INIT_MEMBLOCK_REGIONS].base
!= (phys_addr_t)RED_INACTIVE);
And in memblock_init():
/* Write a marker in the unused last array entry */
memblock.memory.regions[INIT_MEMBLOCK_REGIONS].base = (phys_addr_t)RED_INACTIVE;
memblock.reserved.regions[INIT_MEMBLOCK_REGIONS].base = (phys_addr_t)RED_INACTIVE;
Could this cause any problems? If not, is there anyway to quiet the sparse noise?
Regards,
Hartley
Powered by blists - more mailing lists