public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: xur@google.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v5 2/2] kbuild: distributed build support for Clang ThinLTO
Date: Wed, 5 Nov 2025 22:47:33 +0800	[thread overview]
Message-ID: <202511052257.Bb85ptQG-lkp@intel.com> (raw)
In-Reply-To: <20251028182822.3210436-3-xur@google.com>

Hi,

kernel test robot noticed the following build warnings:

[auto build test WARNING on dcb6fa37fd7bc9c3d2b066329b0d27dedf8becaa]

url:    https://github.com/intel-lab-lkp/linux/commits/xur-google-com/kbuild-move-vmlinux-a-build-rule-to-scripts-Makefile-vmlinux_a/20251029-024527
base:   dcb6fa37fd7bc9c3d2b066329b0d27dedf8becaa
patch link:    https://lore.kernel.org/r/20251028182822.3210436-3-xur%40google.com
patch subject: [PATCH v5 2/2] kbuild: distributed build support for Clang ThinLTO
config: i386-buildonly-randconfig-003-20251105 (https://download.01.org/0day-ci/archive/20251105/202511052257.Bb85ptQG-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251105/202511052257.Bb85ptQG-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/202511052257.Bb85ptQG-lkp@intel.com/

All warnings (new ones prefixed by >>, old ones prefixed by <<):

>> WARNING: modpost: vmlinux: section mismatch in reference: phonet_net_ops.llvm.6273608609221102921+0x8 (section: .data) -> phonet_init_net (section: .init.text)
>> WARNING: modpost: vmlinux: section mismatch in reference: mctp_net_ops.llvm.5397949150189356468+0x8 (section: .data) -> mctp_routes_net_init (section: .init.text)
>> WARNING: modpost: vmlinux: section mismatch in reference: mctp_net_ops.llvm.12518417922465111039+0x8 (section: .data) -> mctp_neigh_net_init (section: .init.text)

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

  reply	other threads:[~2025-11-05 14:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 18:28 [PATCH v5 0/2] kbuild: distributed build support for Clang ThinLTO xur
2025-10-28 18:28 ` [PATCH v5 1/2] kbuild: move vmlinux.a build rule to scripts/Makefile.vmlinux_a xur
2026-03-16 13:33   ` Nicolas Schier
2026-03-16 13:59     ` Miguel Ojeda
2026-03-16 17:27       ` Rong Xu
2026-03-16 17:52         ` Nicolas Schier
2026-03-16 17:59         ` Nathan Chancellor
2026-03-16 18:16           ` Rong Xu
2026-03-16 20:43             ` Nathan Chancellor
2026-03-16 20:53               ` Rong Xu
2026-03-16 21:31                 ` Rong Xu
2025-10-28 18:28 ` [PATCH v5 2/2] kbuild: distributed build support for Clang ThinLTO xur
2025-11-05 14:47   ` kernel test robot [this message]
2025-10-28 19:22 ` [PATCH v5 0/2] " Piotr Gorski
2025-12-04 17:49 ` Nathan Chancellor
2025-12-04 18:36   ` Rong Xu
2026-03-12  8:25 ` Nathan Chancellor
2026-03-12 11:45   ` Nicolas Schier
2026-03-12 17:50     ` Rong Xu
2026-03-13 14:50 ` Nicolas Schier

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=202511052257.Bb85ptQG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=xur@google.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