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:android16-6.12-desktop 1/1] mm/memblock.c:2512:28: warning: cast to pointer from integer of different size
Date: Sat, 30 May 2026 17:10:59 +0800	[thread overview]
Message-ID: <202605301711.sCSHgsPC-lkp@intel.com> (raw)

Hi Jaewon,

FYI, the error/warning still remains.

tree:   https://android.googlesource.com/kernel/common android16-6.12-desktop
head:   3e20a144f5762d10c2d82a5cf65ece4d2c8ea320
commit: b2fbc2411ea7772d758ab4626d83f8aabf29eaf8 [1/1] ANDROID: memblock: introduce memsize showing reserved memory
config: arm-randconfig-002-20260530 (https://download.01.org/0day-ci/archive/20260530/202605301711.sCSHgsPC-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260530/202605301711.sCSHgsPC-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/202605301711.sCSHgsPC-lkp@intel.com/

All warnings (new ones prefixed by >>):

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


vim +2512 mm/memblock.c

  2493	
  2494	static int memblock_memsize_show(struct seq_file *m, void *private)
  2495	{
  2496		int i;
  2497		struct memsize_rgn_struct *rgn;
  2498		unsigned long reserved = 0, reusable = 0;
  2499	
  2500		sort(memsize_rgn, memsize_rgn_count,
  2501		     sizeof(memsize_rgn[0]), memsize_rgn_cmp, NULL);
  2502		for (i = 0; i < memsize_rgn_count; i++) {
  2503			phys_addr_t base, end;
  2504			long size;
  2505	
  2506			rgn = &memsize_rgn[i];
  2507			base = rgn->base;
  2508			size = rgn->size;
  2509			end = base + size;
  2510	
  2511			seq_printf(m, "0x%pK-0x%pK 0x%08lx ( %7lu KB ) %s %s %s\n",
> 2512				   (void *)base, (void *)end,
  2513				   size, DIV_ROUND_UP(size, SZ_1K),
  2514				   rgn->nomap ? "nomap" : "  map",
  2515				   rgn->reusable ? "reusable" : "unusable",
  2516				   rgn->name);
  2517			if (rgn->reusable)
  2518				reusable += (unsigned long)rgn->size;
  2519			else
  2520				reserved += (unsigned long)rgn->size;
  2521		}
  2522	
  2523		seq_puts(m, "\n");
  2524		seq_printf(m, " .unusable  : %7lu KB\n",
  2525			   DIV_ROUND_UP(reserved, SZ_1K));
  2526		seq_printf(m, " .reusable  : %7lu KB\n",
  2527			   DIV_ROUND_UP(reusable, SZ_1K));
  2528		return 0;
  2529	}
  2530	

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

                 reply	other threads:[~2026-05-30  9:11 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=202605301711.sCSHgsPC-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.