From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: {standard input}:4543: Error: Insn bl has an instruction mpyuw with limm in its delay slot.
Date: Sun, 15 Nov 2026 14:54:24 +0100 [thread overview]
Message-ID: <202611151441.JKvIVIOA-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "too many reports for this commit | /zdci/kbuild/indicators/6c/6c2fd7a71e7ab490a0a9d591486d923712012f59-reported_build_error_fbc-error"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Vivek Aknurwar <vivek.aknurwar@oss.qualcomm.com>
CC: Sudeep Holla <sudeep.holla@arm.com>
CC: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
CC: Alexey Klimov <alexey.klimov@linaro.org>
Hi Vivek,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 23c62304dde29abe92013d85910d03a77dada35d
commit: 6c2fd7a71e7ab490a0a9d591486d923712012f59 firmware: arm_scmi: Increase performance MAX_OPPS limit to 64
date: 11 months ago
:::::: branch date: 19 hours ago
:::::: commit date: 11 months ago
config: arc-randconfig-2001-20261115 (https://download.01.org/0day-ci/archive/20261115/202611151441.JKvIVIOA-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 16.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261115/202611151441.JKvIVIOA-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
| Fixes: 6c2fd7a71e7a ("firmware: arm_scmi: Increase performance MAX_OPPS limit to 64")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202611151441.JKvIVIOA-lkp@intel.com/
All errors (new ones prefixed by >>):
Assembler messages:
>> {standard input}:4543: Error: Insn bl has an instruction mpyuw with limm in its delay slot.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-15 13:54 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=202611151441.JKvIVIOA-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.