From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH RFC] ALSA: control: Use xarray for faster lookups
Date: Fri, 29 Oct 2021 08:36:07 +0800 [thread overview]
Message-ID: <202110290841.R9Ch2AJ1-lkp@intel.com> (raw)
In-Reply-To: <20211028130027.18764-1-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1802 bytes --]
Hi Takashi,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on tiwai-sound/for-next]
[also build test ERROR on v5.15-rc7 next-20211028]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Takashi-Iwai/ALSA-control-Use-xarray-for-faster-lookups/20211028-210215
base: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next
config: mips-rs90_defconfig (attached as .config)
compiler: mipsel-linux-gcc (GCC) 11.2.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://github.com/0day-ci/linux/commit/d9e50e9647a202433a7b1c261b0edb0021f16004
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Takashi-Iwai/ALSA-control-Use-xarray-for-faster-lookups/20211028-210215
git checkout d9e50e9647a202433a7b1c261b0edb0021f16004
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=mips SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
mipsel-linux-ld: sound/core/control.o: in function `add_hash_entries':
>> control.c:(.text.add_hash_entries+0x74): undefined reference to `xa_store_range'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 19411 bytes --]
next prev parent reply other threads:[~2021-10-29 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 13:00 [PATCH RFC] ALSA: control: Use xarray for faster lookups Takashi Iwai
2021-10-28 22:34 ` kernel test robot
2021-10-28 23:13 ` kernel test robot
2021-10-29 0:29 ` kernel test robot
2021-10-29 0:29 ` kernel test robot
2021-10-29 0:36 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-30 1:13 kernel test robot
2021-10-31 14:17 ` kernel test robot
2021-10-31 14:17 ` 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=202110290841.R9Ch2AJ1-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.