From: Joonwon Kang <joonwonkang@google.com>
To: lkp@intel.com
Cc: joonwonkang@google.com, oe-kbuild-all@lists.linux.dev
Subject: Re: mm/percpu-stats.c:125:9: error: aggregate value used where an integer was expected
Date: Fri, 15 May 2026 04:41:01 +0000 [thread overview]
Message-ID: <20260515044101.2517293-1-joonwonkang@google.com> (raw)
In-Reply-To: <202605150328.mn2hv1fZ-lkp@intel.com>
> tree: https://github.com/intel-lab-lkp/linux/commits/Joonwon-Kang/percpu-Do-not-trust-hint-starts-when-they-are-not-set/20260513-070153
> head: 53a3f421840a59abecd38cc1be7c4f1d4516c3f1
> commit: 27e83e031c0de38ffad3fe513474bff375c2a896 percpu: Introduce struct pcpu_region
> date: 2 days ago
> config: x86_64-randconfig-2005-20250721 (https://download.01.org/0day-ci/archive/20260515/202605150328.mn2hv1fZ-lkp@intel.com/config)
> compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260515/202605150328.mn2hv1fZ-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/202605150328.mn2hv1fZ-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> mm/percpu-stats.c: In function 'chunk_map_stats':
> >> mm/percpu-stats.c:125:9: error: aggregate value used where an integer was expected
> 125 | P("contig_bytes", chunk_md->contig_hint * PCPU_MIN_ALLOC_SIZE);
> | ^
Hi bot,
I guess you picked up an older version than v5. This issue has been fixed
since v5. You can also find it in the latest version v6 [1].
[1] https://lore.kernel.org/all/20260513085117.1024175-3-joonwonkang@google.com/
Thanks,
Joonwon Kang
next prev parent reply other threads:[~2026-05-15 4:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 1:14 mm/percpu-stats.c:125:9: error: aggregate value used where an integer was expected kernel test robot
2026-05-15 4:41 ` Joonwon Kang [this message]
2026-05-15 11:01 ` Philip Li
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=20260515044101.2517293-1-joonwonkang@google.com \
--to=joonwonkang@google.com \
--cc=lkp@intel.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.