From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH] modpost: drop '*_probe' from section check whitelist
Date: Thu, 30 Oct 2025 18:03:39 +0800 [thread overview]
Message-ID: <202510301718.aYPBxGbE-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "only suspicious fbc files changed"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20251020091613.22562-1-johan@kernel.org>
References: <20251020091613.22562-1-johan@kernel.org>
TO: Johan Hovold <johan@kernel.org>
TO: Nathan Chancellor <nathan@kernel.org>
TO: Nicolas Schier <nicolas.schier@linux.dev>
CC: Masahiro Yamada <masahiroy@kernel.org>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: linux-kbuild@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: Johan Hovold <johan@kernel.org>
Hi Johan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.18-rc3 next-20251029]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Johan-Hovold/modpost-drop-_probe-from-section-check-whitelist/20251020-171732
base: linus/master
patch link: https://lore.kernel.org/r/20251020091613.22562-1-johan%40kernel.org
patch subject: [PATCH] modpost: drop '*_probe' from section check whitelist
:::::: branch date: 10 days ago
:::::: commit date: 10 days ago
config: xtensa-randconfig-001-20251027 (https://download.01.org/0day-ci/archive/20251030/202510301718.aYPBxGbE-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251030/202510301718.aYPBxGbE-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/r/202510301718.aYPBxGbE-lkp@intel.com/
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> WARNING: modpost: vmlinux: section mismatch in reference: nxp_stm_probe+0x0 (section: .data) -> set_reset_devices (section: .init.text)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-10-30 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 10:03 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-20 15:52 [PATCH] modpost: drop '*_probe' from section check whitelist kernel test robot
2025-10-20 9:16 Johan Hovold
2025-10-21 0:20 ` kernel test robot
2025-10-22 20:39 ` Nathan Chancellor
2025-11-12 16:48 ` Johan Hovold
2025-11-14 4:16 ` Nathan Chancellor
2025-11-14 8:45 ` Johan Hovold
2025-12-16 1:11 ` Johan Hovold
2025-11-15 15:36 ` Thomas Gleixner
2025-12-16 13:13 ` 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=202510301718.aYPBxGbE-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 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.