All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Mark Brown <broonie@kernel.org>
Subject: [broonie-ci:files2POTT 66/93] undefined reference to `slim_stream_prepare'
Date: Thu, 8 Sep 2022 21:03:08 +0800	[thread overview]
Message-ID: <202209082046.AZVfl0da-lkp@intel.com> (raw)

Hi Krzysztof,

FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git files2POTT
head:   e9e7df88996d64544178f48b0299dfe736c6aa22
commit: 5b7f4e5de61ba8c44317718936864da29eeba62a [66/93] ASoC: codecs: allow compile testing without MFD drivers
config: microblaze-buildonly-randconfig-r004-20220907 (https://download.01.org/0day-ci/archive/20220908/202209082046.AZVfl0da-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git/commit/?id=5b7f4e5de61ba8c44317718936864da29eeba62a
        git remote add broonie-ci https://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git
        git fetch --no-tags broonie-ci files2POTT
        git checkout 5b7f4e5de61ba8c44317718936864da29eeba62a
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=microblaze SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

Note: the broonie-ci/files2POTT HEAD e9e7df88996d64544178f48b0299dfe736c6aa22 builds fine.
      It only hurts bisectability.

All errors (new ones prefixed by >>):

   microblaze-linux-ld: sound/soc/codecs/wcd934x.o: in function `wcd934x_trigger':
>> (.text+0x3f8): undefined reference to `slim_stream_prepare'
>> microblaze-linux-ld: (.text+0x404): undefined reference to `slim_stream_enable'
>> microblaze-linux-ld: (.text+0x434): undefined reference to `slim_stream_unprepare'
>> microblaze-linux-ld: (.text+0x440): undefined reference to `slim_stream_disable'
   microblaze-linux-ld: sound/soc/codecs/wcd934x.o: in function `wcd934x_slim_set_hw_params':
>> (.text+0x3854): undefined reference to `slim_stream_allocate'
   microblaze-linux-ld: sound/soc/codecs/wcd934x.o: in function `wcd934x_codec_probe':
>> (.text+0x44c4): undefined reference to `of_slim_get_device'
>> microblaze-linux-ld: (.text+0x44dc): undefined reference to `slim_get_logical_addr'
>> microblaze-linux-ld: (.text+0x4500): undefined reference to `__regmap_init_slimbus'

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

             reply	other threads:[~2022-09-08 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 13:03 kernel test robot [this message]
2022-09-08 13:16 ` [broonie-ci:files2POTT 66/93] undefined reference to `slim_stream_prepare' Krzysztof Kozlowski
2022-09-08 13:16   ` Krzysztof Kozlowski

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=202209082046.AZVfl0da-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=broonie@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.