From: kernel test robot <lkp@intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [mark:arm64/ftrace/per-callsite-ops 2/4] arch/riscv/kernel/setup.c:318:1: warning: 'text_section' attribute directive ignored
Date: Tue, 7 Jun 2022 03:25:25 +0800 [thread overview]
Message-ID: <202206070358.Tnsgqt6p-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git arm64/ftrace/per-callsite-ops
head: 7f0d1ffaab77795e4ca97db4a901cc347c850ff7
commit: efc001292934b744fa4c8147668fa4bd0ee909bf [2/4] WIP: incomplete alignment hacks
config: riscv-allnoconfig (https://download.01.org/0day-ci/archive/20220607/202206070358.Tnsgqt6p-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/commit/?id=efc001292934b744fa4c8147668fa4bd0ee909bf
git remote add mark https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git
git fetch --no-tags mark arm64/ftrace/per-callsite-ops
git checkout efc001292934b744fa4c8147668fa4bd0ee909bf
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash arch/riscv/kernel/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/riscv/kernel/setup.c:318:1: warning: 'text_section' attribute directive ignored [-Wattributes]
318 | subsys_initcall(topology_init);
| ^~~~~~~~~~~~~~~
vim +/text_section +318 arch/riscv/kernel/setup.c
f1e58583b9c7ce Atish Patra 2020-03-17 301
f1e58583b9c7ce Atish Patra 2020-03-17 302 static int __init topology_init(void)
f1e58583b9c7ce Atish Patra 2020-03-17 303 {
4f0e8eef772ee4 Atish Patra 2020-11-18 304 int i, ret;
4f0e8eef772ee4 Atish Patra 2020-11-18 305
f1e58583b9c7ce Atish Patra 2020-03-17 306 for_each_possible_cpu(i) {
f1e58583b9c7ce Atish Patra 2020-03-17 307 struct cpu *cpu = &per_cpu(cpu_devices, i);
f1e58583b9c7ce Atish Patra 2020-03-17 308
f1e58583b9c7ce Atish Patra 2020-03-17 309 cpu->hotpluggable = cpu_has_hotplug(i);
4f0e8eef772ee4 Atish Patra 2020-11-18 310 ret = register_cpu(cpu, i);
4f0e8eef772ee4 Atish Patra 2020-11-18 311 if (unlikely(ret))
4f0e8eef772ee4 Atish Patra 2020-11-18 312 pr_warn("Warning: %s: register_cpu %d failed (%d)\n",
4f0e8eef772ee4 Atish Patra 2020-11-18 313 __func__, i, ret);
f1e58583b9c7ce Atish Patra 2020-03-17 314 }
f1e58583b9c7ce Atish Patra 2020-03-17 315
f1e58583b9c7ce Atish Patra 2020-03-17 316 return 0;
f1e58583b9c7ce Atish Patra 2020-03-17 317 }
f1e58583b9c7ce Atish Patra 2020-03-17 @318 subsys_initcall(topology_init);
19a00869028f4a Atish Patra 2020-11-04 319
:::::: The code at line 318 was first introduced by commit
:::::: f1e58583b9c7ceae7f11646e9edf2561d67f29c9 RISC-V: Support cpu hotplug
:::::: TO: Atish Patra <atish.patra@wdc.com>
:::::: CC: Palmer Dabbelt <palmerdabbelt@google.com>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-06 19:26 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=202206070358.Tnsgqt6p-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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
all inboxes | Powered by JetHome®