From: kernel test robot <lkp@intel.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:mm-nonmm-unstable 22/23] lib/group_cpus.c:352:16: error: array initializer must be an initializer list
Date: Sun, 14 Jan 2024 01:40:11 +0800 [thread overview]
Message-ID: <202401140117.pwAcsXAT-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
head: 3d69c575710800c9a4a58e94c157697310e32027
commit: a868f9c8816cb72f983d1ff940b0938737fe8ee7 [22/23] lib/group_cpus: fix initialization section in group_cpus_evenly()
config: i386-randconfig-011-20240113 (https://download.01.org/0day-ci/archive/20240114/202401140117.pwAcsXAT-lkp@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240114/202401140117.pwAcsXAT-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/202401140117.pwAcsXAT-lkp@intel.com/
All errors (new ones prefixed by >>):
>> lib/group_cpus.c:352:16: error: array initializer must be an initializer list
352 | cpumask_var_t npresmsk __free(free_cpumask_var) = NULL;
| ^
1 error generated.
vim +352 lib/group_cpus.c
332
333 /**
334 * group_cpus_evenly - Group all CPUs evenly per NUMA/CPU locality
335 * @numgrps: number of groups
336 *
337 * Return: cpumask array if successful, NULL otherwise. And each element
338 * includes CPUs assigned to this group
339 *
340 * Try to put close CPUs from viewpoint of CPU and NUMA locality into
341 * same group, and run two-stage grouping:
342 * 1) allocate present CPUs on these groups evenly first
343 * 2) allocate other possible CPUs on these groups evenly
344 *
345 * We guarantee in the resulted grouping that all CPUs are covered, and
346 * no same CPU is assigned to multiple groups
347 */
348 struct cpumask *group_cpus_evenly(unsigned int numgrps)
349 {
350 cpumask_var_t *node_to_cpumask __free(free_node_to_cpumask) = alloc_node_to_cpumask();
351 struct cpumask *masks __free(kfree) = kcalloc(numgrps, sizeof(*masks), GFP_KERNEL);
> 352 cpumask_var_t npresmsk __free(free_cpumask_var) = NULL;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-01-13 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 17:40 kernel test robot [this message]
2024-01-16 22:55 ` Nathan Chancellor
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=202401140117.pwAcsXAT-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yury.norov@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox