linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dawei Li <dawei.li@shingroup.cn>
Cc: 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 15/17] lib/cpumask.c:61: warning: cannot understand function prototype: 'struct kmem_cache *cpumask_cache __ro_after_init; '
Date: Wed, 20 Mar 2024 23:51:42 +0800	[thread overview]
Message-ID: <202403202344.Aao4CzXG-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
head:   fa63bc7d26007e1353fa90bb06cc37966bd1513a
commit: 61ec2810d92f31b0ef8b30b08ee1d1e1ffc45ddc [15/17] cpumask: create dedicated kmem cache for cpumask var
config: parisc-defconfig (https://download.01.org/0day-ci/archive/20240320/202403202344.Aao4CzXG-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240320/202403202344.Aao4CzXG-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/202403202344.Aao4CzXG-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> lib/cpumask.c:61: warning: cannot understand function prototype: 'struct kmem_cache *cpumask_cache __ro_after_init; '


vim +61 lib/cpumask.c

    41	
    42	/* These are not inline because of header tangles. */
    43	#ifdef CONFIG_CPUMASK_OFFSTACK
    44	/**
    45	 * alloc_cpumask_var_node - allocate a struct cpumask on a given node
    46	 * @mask: pointer to cpumask_var_t where the cpumask is returned
    47	 * @flags: GFP_ flags
    48	 * @node: memory node from which to allocate or %NUMA_NO_NODE
    49	 *
    50	 * Only defined when CONFIG_CPUMASK_OFFSTACK=y, otherwise is
    51	 * a nop returning a constant 1 (in <linux/cpumask.h>).
    52	 *
    53	 * Return: TRUE if memory allocation succeeded, FALSE otherwise.
    54	 *
    55	 * In addition, mask will be NULL if this fails.  Note that gcc is
    56	 * usually smart enough to know that mask can never be NULL if
    57	 * CONFIG_CPUMASK_OFFSTACK=n, so does code elimination in that case
    58	 * too.
    59	 */
    60	
  > 61	static struct kmem_cache *cpumask_cache __ro_after_init;
    62	

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


                 reply	other threads:[~2024-03-20 15:52 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=202403202344.Aao4CzXG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dawei.li@shingroup.cn \
    --cc=linux-mm@kvack.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox