From: kernel test robot <lkp@intel.com>
To: xur@google.com, "Alexey Gladkov" <legion@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Bill Wendling" <morbo@google.com>,
"Han Shen" <shenhan@google.com>, "Ingo Molnar" <mingo@kernel.org>,
"Josh Poimboeuf" <jpoimboe@kernel.org>,
"Justin Stitt" <justinstitt@google.com>,
"Kees Cook" <kees@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Nicolas Schier" <nicolas.schier@linux.dev>,
"Peter Zijlstra" <peterz@infradead.org>,
"Tamir Duberstein" <tamird@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Yabin Cui" <yabinc@google.com>,
"Sriraman Tallam" <tmsriram@google.com>
Cc: <llvm@lists.linux.dev>, <oe-kbuild-all@lists.linux.dev>,
<linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Rong Xu <xur@google.com>
Subject: Re: [PATCH 2/4] kbuild: Disable AutoFDO and Propeller flags for kernel modules
Date: Sun, 12 Oct 2025 10:13:58 +0800 [thread overview]
Message-ID: <aOsO5gO+5/OkZXVn@rli9-mobl> (raw)
In-Reply-To: <20251010210134.2066321-2-xur@google.com>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on kees/for-next/kspp]
[also build test ERROR on linus/master kees/for-next/pstore v6.17 next-20251010]
[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/xur-google-com/kbuild-Disable-AutoFDO-and-Propeller-flags-for-kernel-modules/20251011-050345
base: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/kspp
patch link: https://lore.kernel.org/r/20251010210134.2066321-2-xur%40google.com
patch subject: [PATCH 2/4] kbuild: Disable AutoFDO and Propeller flags for kernel modules
:::::: branch date: 26 hours ago
:::::: commit date: 26 hours ago
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20251012/202510120709.Wx3q4Ppg-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251012/202510120709.Wx3q4Ppg-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/202510120709.Wx3q4Ppg-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: -r and -pie may not be used together
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-12 2:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 21:01 [PATCH 1/4] kbuild: Fix Propeller flags xur
2025-10-10 21:01 ` [PATCH 2/4] kbuild: Disable AutoFDO and Propeller flags for kernel modules xur
2025-10-12 2:13 ` kernel test robot
2025-10-14 19:02 ` Rong Xu
2025-10-12 2:13 ` kernel test robot [this message]
2025-10-14 19:03 ` Rong Xu
2025-10-10 21:01 ` [PATCH 3/4] kbuild: Remove MFS flags from Propeller profile generate builds xur
2025-10-10 21:01 ` [PATCH 4/4] kbuild: Add config to assert profile accuracy for aggressive optimization xur
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=aOsO5gO+5/OkZXVn@rli9-mobl \
--to=lkp@intel.com \
--cc=aliceryhl@google.com \
--cc=ardb@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=legion@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=mingo@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nicolas.schier@linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=shenhan@google.com \
--cc=tamird@gmail.com \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
--cc=tmsriram@google.com \
--cc=xur@google.com \
--cc=yabinc@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