From: kernel test robot <lkp@intel.com>
To: Lachlan Hodges <lachlan.hodges@morsemicro.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Pope <andrew.pope@morsemicro.com>,
Arien Judge <arien.judge@morsemicro.com>,
Ayman Grais <ayman.grais@morsemicro.com>,
Bassem Dawood <bassem@morsemicro.com>,
Chetan Mistry <chetan.mistry@morsemicro.com>,
Dan Callaghan <dan.callaghan@morsemicro.com>,
James Herbert <james.herbert@morsemicro.com>,
Sahand Maleki <sahand.maleki@morsemicro.com>,
Simon Wadsworth <simon@morsemicro.com>
Subject: [linux-next:master 3244/10444] {standard input}:191: Error: Insn b has an instruction mpyuw with limm in its delay slot.
Date: Fri, 31 Jul 2026 05:48:52 +0800 [thread overview]
Message-ID: <202607310532.ggqUOCi6-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 78bc8af4affb9a732504eb22eeac7d1e50883853
commit: b1906cea00b021acea22460225401d5b27bc7c36 [3244/10444] wifi: mm81x: add mm81x Wi-Fi HaLow driver
config: arc-allmodconfig (https://download.01.org/0day-ci/archive/20260731/202607310532.ggqUOCi6-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260731/202607310532.ggqUOCi6-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/202607310532.ggqUOCi6-lkp@intel.com/
All errors (new ones prefixed by >>):
Assembler messages:
>> {standard input}:191: Error: Insn b 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-07-30 21:49 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=202607310532.ggqUOCi6-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew.pope@morsemicro.com \
--cc=arien.judge@morsemicro.com \
--cc=ayman.grais@morsemicro.com \
--cc=bassem@morsemicro.com \
--cc=chetan.mistry@morsemicro.com \
--cc=dan.callaghan@morsemicro.com \
--cc=james.herbert@morsemicro.com \
--cc=lachlan.hodges@morsemicro.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sahand.maleki@morsemicro.com \
--cc=simon@morsemicro.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.