From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18-lts 1/1] mm/memblock.c:2169:13: warning: variable 'memsize_reusable_size' set but not used
Date: Thu, 29 Oct 2026 16:13:35 +0800 [thread overview]
Message-ID: <202610291512.oEmOZYbF-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18-lts
head: 7aa62a531907e90da2a2bcd2aa20be3e26c4d37e
commit: e501b42d39e7c088623b7ab375252b9ce1328eda [1/1] ANDROID: memblock: support memsize reusable to consider as reusable
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20261029/202610291512.oEmOZYbF-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 1da436a23e613c425fc9b868fc8deb979ede47a4)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261029/202610291512.oEmOZYbF-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/202610291512.oEmOZYbF-lkp@intel.com/
All warnings (new ones prefixed by >>):
mm/memblock.c:2164:13: warning: variable 'memsize_memmap' set but not used [-Wunused-but-set-global]
2164 | static long memsize_memmap;
| ^
mm/memblock.c:2165:22: warning: variable 'memsize_code' set but not used [-Wunused-but-set-global]
2165 | static unsigned long memsize_code __initdata_memblock;
| ^
mm/memblock.c:2166:22: warning: variable 'memsize_data' set but not used [-Wunused-but-set-global]
2166 | static unsigned long memsize_data __initdata_memblock;
| ^
mm/memblock.c:2167:22: warning: variable 'memsize_ro' set but not used [-Wunused-but-set-global]
2167 | static unsigned long memsize_ro __initdata_memblock;
| ^
mm/memblock.c:2168:22: warning: variable 'memsize_bss' set but not used [-Wunused-but-set-global]
2168 | static unsigned long memsize_bss __initdata_memblock;
| ^
>> mm/memblock.c:2169:13: warning: variable 'memsize_reusable_size' set but not used [-Wunused-but-set-global]
2169 | static long memsize_reusable_size;
| ^
6 warnings generated.
vim +/memsize_reusable_size +2169 mm/memblock.c
2161
2162 static struct memsize_rgn_struct memsize_rgn[CONFIG_MAX_MEMBLOCK_MEMSIZE] __initdata_memblock;
2163 static int memsize_rgn_count __initdata_memblock;
2164 static long memsize_memmap;
2165 static unsigned long memsize_code __initdata_memblock;
2166 static unsigned long memsize_data __initdata_memblock;
2167 static unsigned long memsize_ro __initdata_memblock;
2168 static unsigned long memsize_bss __initdata_memblock;
> 2169 static long memsize_reusable_size;
2170
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-29 8:14 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=202610291512.oEmOZYbF-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.