All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6 3/3] mm/memblock.c:2327:28: warning: cast to pointer from integer of different size
Date: Fri, 18 Sep 2026 11:38:51 +0800	[thread overview]
Message-ID: <202609181052.UYPD9SXQ-lkp@intel.com> (raw)

Hi Jaewon,

FYI, the error/warning still remains.

tree:   https://android.googlesource.com/kernel/common android15-6.6
head:   cdc3592a0ce26ec13098dd267d8c47b97aa03b49
commit: 3368d09174c6e8f3759bd201dbe6ca20ed0cd0e0 [3/3] FROMLIST: memblock: introduce memsize showing reserved memory
config: arm-randconfig-r1300-20260918 (https://download.01.org/0day-ci/archive/20260918/202609181052.UYPD9SXQ-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 15.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260918/202609181052.UYPD9SXQ-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609181052.UYPD9SXQ-lkp@intel.com/

All warnings (new ones prefixed by >>):

   mm/memblock.c: In function 'memblock_memsize_show':
>> mm/memblock.c:2327:28: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
    2327 |                            (void *)base, (void *)end,
         |                            ^
   mm/memblock.c:2327:42: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
    2327 |                            (void *)base, (void *)end,
         |                                          ^


vim +2327 mm/memblock.c

  2308	
  2309	static int memblock_memsize_show(struct seq_file *m, void *private)
  2310	{
  2311		int i;
  2312		struct memsize_rgn_struct *rgn;
  2313		unsigned long reserved = 0, reusable = 0;
  2314	
  2315		sort(memsize_rgn, memsize_rgn_count,
  2316		     sizeof(memsize_rgn[0]), memsize_rgn_cmp, NULL);
  2317		for (i = 0; i < memsize_rgn_count; i++) {
  2318			phys_addr_t base, end;
  2319			long size;
  2320	
  2321			rgn = &memsize_rgn[i];
  2322			base = rgn->base;
  2323			size = rgn->size;
  2324			end = base + size;
  2325	
  2326			seq_printf(m, "0x%pK-0x%pK 0x%08lx ( %7lu KB ) %s %s %s\n",
> 2327				   (void *)base, (void *)end,
  2328				   size, DIV_ROUND_UP(size, SZ_1K),
  2329				   rgn->nomap ? "nomap" : "  map",
  2330				   rgn->reusable ? "reusable" : "unusable",
  2331				   rgn->name);
  2332			if (rgn->reusable)
  2333				reusable += (unsigned long)rgn->size;
  2334			else
  2335				reserved += (unsigned long)rgn->size;
  2336		}
  2337	
  2338		seq_puts(m, "\n");
  2339		seq_printf(m, " .unusable  : %7lu KB\n",
  2340			   DIV_ROUND_UP(reserved, SZ_1K));
  2341		seq_printf(m, " .reusable  : %7lu KB\n",
  2342			   DIV_ROUND_UP(reusable, SZ_1K));
  2343		return 0;
  2344	}
  2345	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-09-18  3:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202609181052.UYPD9SXQ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.