From: kernel test robot <lkp@intel.com>
To: Woradorn Laodhanadhaworn <woradorn.laon@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, Steven Rostedt <rostedt@goodmis.org>
Subject: [trace:trace/core 16/16] WARNING: modpost: vmlinux: section mismatch in reference: __list_add+0x7c (section: .text.unlikely) -> initcall_level_names (section: .init.data)
Date: Thu, 30 Jul 2026 17:54:12 +0800 [thread overview]
Message-ID: <202607301724.FWw4uuO3-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace trace/core
head: c33330b2ec170dd38b3284a72bc6a07a49cc9a65
commit: c33330b2ec170dd38b3284a72bc6a07a49cc9a65 [16/16] tracing: Use seq_buf for string concatenation
config: xtensa-randconfig-r072-20260730 (https://download.01.org/0day-ci/archive/20260730/202607301724.FWw4uuO3-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 13.4.0
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260730/202607301724.FWw4uuO3-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/202607301724.FWw4uuO3-lkp@intel.com/
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> WARNING: modpost: vmlinux: section mismatch in reference: __list_add+0x7c (section: .text.unlikely) -> initcall_level_names (section: .init.data)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-07-30 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 9:54 kernel test robot [this message]
2026-07-30 13:39 ` [trace:trace/core 16/16] WARNING: modpost: vmlinux: section mismatch in reference: __list_add+0x7c (section: .text.unlikely) -> initcall_level_names (section: .init.data) Steven Rostedt
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=202607301724.FWw4uuO3-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=woradorn.laon@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 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.