From: kernel test robot <lkp@intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [freescale-fslc:pr/639 257/24603] make[5]: *** No rule to make target 'sound/soc/sof/intel/snd-sof-intel-ipc.o', needed by 'sound/soc/sof/intel/built-in.a'.
Date: Sun, 15 Oct 2023 22:22:34 +0800 [thread overview]
Message-ID: <202310152213.tuGAoB0t-lkp@intel.com> (raw)
Hi Daniel,
First bad commit (maybe != root cause):
tree: https://github.com/Freescale/linux-fslc pr/639
head: 857fbf7cebaba3b1ffccc558deee1d13ac0e11d7
commit: 51b86bcaf08f3cd48122cdbee63e8f469dcb3e64 [257/24603] LF-3774-1 ASoC: sof: Make Intel IPC stream ops generic
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20231015/202310152213.tuGAoB0t-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231015/202310152213.tuGAoB0t-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/202310152213.tuGAoB0t-lkp@intel.com/
All errors (new ones prefixed by >>):
>> make[5]: *** No rule to make target 'sound/soc/sof/intel/snd-sof-intel-ipc.o', needed by 'sound/soc/sof/intel/built-in.a'.
make[5]: *** [scripts/Makefile.build:277: sound/soc/sof/intel/pci-tng.o] Error 1
make[5]: Target '__build' not remade because of errors.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-10-15 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 14:22 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-31 18:36 [freescale-fslc:pr/639 257/24603] make[5]: *** No rule to make target 'sound/soc/sof/intel/snd-sof-intel-ipc.o', needed by 'sound/soc/sof/intel/built-in.a' kernel test robot
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=202310152213.tuGAoB0t-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=otavio@ossystems.com.br \
/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.