From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
Bard Liao <bard.liao@intel.com>
Subject: Re: ld.lld: error: undefined symbol: iosf_mbi_available
Date: Wed, 17 Jul 2024 13:43:35 +0200 [thread overview]
Message-ID: <05954a59-2bef-4262-bd91-cfe21d2381f2@linux.intel.com> (raw)
In-Reply-To: <202407160704.zpdhJ8da-lkp@intel.com>
On 7/16/24 01:07, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 3e7819886281e077e82006fe4804b0d6b0f5643b
> commit: 8d4ba1be3d2257606e04aff412829d8972670750 ASoC: SOF: pci: split PCI into different drivers
> date: 3 years, 4 months ago
This doesn't seem to be a problem on the latest code? was it intentional
to report a problem on such an old commit?
> config: i386-buildonly-randconfig-004-20240716 (https://download.01.org/0day-ci/archive/20240716/202407160704.zpdhJ8da-lkp@intel.com/config)
> compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240716/202407160704.zpdhJ8da-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/202407160704.zpdhJ8da-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>>> ld.lld: error: undefined symbol: iosf_mbi_available
> >>> referenced by byt.c
> >>> soc/sof/intel/byt.o:(byt_machine_select) in archive sound/built-in.a
> --
>>> ld.lld: error: undefined symbol: iosf_mbi_read
> >>> referenced by byt.c
> >>> soc/sof/intel/byt.o:(byt_machine_select) in archive sound/built-in.a
>
next prev parent reply other threads:[~2024-07-17 11:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 23:07 ld.lld: error: undefined symbol: iosf_mbi_available kernel test robot
2024-07-17 11:43 ` Pierre-Louis Bossart [this message]
2024-07-17 20:28 ` Nathan Chancellor
2024-07-18 7:26 ` Takashi Iwai
2024-07-18 8:23 ` Pierre-Louis Bossart
2024-07-18 8:59 ` Takashi Iwai
2024-07-18 9:12 ` Pierre-Louis Bossart
2024-07-18 15:02 ` Takashi Iwai
2024-07-18 15:16 ` Pierre-Louis Bossart
2024-07-18 15:36 ` Takashi Iwai
2024-07-19 6:42 ` Pierre-Louis Bossart
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=05954a59-2bef-4262-bd91-cfe21d2381f2@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=bard.liao@intel.com \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tiwai@suse.de \
/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