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 07:13:45 +0800 [thread overview]
Message-ID: <202110290726.Kz4fDmLW-lkp@intel.com> (raw)
In-Reply-To: <20211028130027.18764-1-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 5295 bytes --]
Hi Takashi,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on tiwai-sound/for-next]
[also build test WARNING 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-randconfig-s031-20211028 (attached as .config)
compiler: mips64-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# 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
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
command-line: note: in included file:
builtin:1:9: sparse: sparse: preprocessor token __ATOMIC_ACQUIRE redefined
builtin:0:0: sparse: this was the original definition
builtin:1:9: sparse: sparse: preprocessor token __ATOMIC_SEQ_CST redefined
builtin:0:0: sparse: this was the original definition
builtin:1:9: sparse: sparse: preprocessor token __ATOMIC_ACQ_REL redefined
builtin:0:0: sparse: this was the original definition
builtin:1:9: sparse: sparse: preprocessor token __ATOMIC_RELEASE redefined
builtin:0:0: sparse: this was the original definition
>> sound/core/control.c:377:11: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long h @@ got restricted snd_ctl_elem_iface_t const [usertype] iface @@
sound/core/control.c:377:11: sparse: expected unsigned long h
sound/core/control.c:377:11: sparse: got restricted snd_ctl_elem_iface_t const [usertype] iface
sound/core/control.c:890:17: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control.c:890:26: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control.c:891:17: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control.c:891:26: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control.c:910:48: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control.c:1604:40: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control.c: note: in included file:
sound/core/control_compat.c:193:21: sparse: sparse: incorrect type in assignment (different base types) @@ expected int [assigned] err @@ got restricted snd_ctl_elem_type_t [usertype] type @@
sound/core/control_compat.c:193:21: sparse: expected int [assigned] err
sound/core/control_compat.c:193:21: sparse: got restricted snd_ctl_elem_type_t [usertype] type
sound/core/control_compat.c:203:14: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control_compat.c:205:14: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control_compat.c:207:14: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control_compat.c:209:14: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control_compat.c:237:21: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control_compat.c:238:21: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control_compat.c:269:21: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
sound/core/control_compat.c:270:21: sparse: sparse: restricted snd_ctl_elem_type_t degrades to integer
vim +377 sound/core/control.c
366
367 /* Compute a hash key for the corresponding ctl id
368 * It's for the name lookup, hence the numid is excluded.
369 * The hash key is bound in LONG_MAX to be used for Xarray key.
370 */
371 #define MULTIPLIER 37
372 static unsigned long get_ctl_id_hash(const struct snd_ctl_elem_id *id)
373 {
374 unsigned long h;
375 const unsigned char *p;
376
> 377 h = id->iface;
378 h = MULTIPLIER * h + id->device;
379 h = MULTIPLIER * h + id->subdevice;
380 for (p = id->name; *p; p++)
381 h = MULTIPLIER * h + *p;
382 h = MULTIPLIER * h + id->index;
383 h &= LONG_MAX;
384 return h;
385 }
386
---
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: 33872 bytes --]
next prev parent reply other threads:[~2021-10-28 23:13 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 [this message]
2021-10-29 0:29 ` kernel test robot
2021-10-29 0:29 ` kernel test robot
2021-10-29 0:36 ` kernel test robot
-- 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=202110290726.Kz4fDmLW-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.