From: kernel test robot <lkp@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: [tip:x86/apic 1/2] include/linux/smp.h:221:27: error: 'setup_max_cpus' defined but not used
Date: Tue, 27 Feb 2024 10:55:46 +0800 [thread overview]
Message-ID: <202402271008.YvpQ54cP-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/apic
head: 62aaed88843a9a69b5614f99ec4a2930edd09658
commit: 429bb0269058e2e1f4ab69a0d33d374933aa15b9 [1/2] smp: Provide 'setup_max_cpus' definition on UP too
config: arm-randconfig-004-20240227 (https://download.01.org/0day-ci/archive/20240227/202402271008.YvpQ54cP-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240227/202402271008.YvpQ54cP-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/202402271008.YvpQ54cP-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/lockdep.h:14,
from include/linux/spinlock.h:63,
from include/linux/mmzone.h:8,
from include/linux/gfp.h:7,
from include/linux/umh.h:4,
from include/linux/kmod.h:9,
from include/linux/module.h:17,
from lib/test_bitops.c:9:
>> include/linux/smp.h:221:27: error: 'setup_max_cpus' defined but not used [-Werror=unused-const-variable=]
221 | static const unsigned int setup_max_cpus = 0;
| ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/setup_max_cpus +221 include/linux/smp.h
220
> 221 static const unsigned int setup_max_cpus = 0;
222
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-27 2:59 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=202402271008.YvpQ54cP-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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