From: kbuild test robot <lkp@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, kbuild-all@lists.01.org
Subject: [alsa-devel] [sound:topic/ctl-validation 162/174] ./usr/include/sound/hdsp.h:35:2: error: unknown type name '__u32'
Date: Tue, 31 Dec 2019 03:18:10 +0800 [thread overview]
Message-ID: <201912310306.vQMe1dAi%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
Hi Takashi,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git topic/ctl-validation
head: a04b915fd997c2e9ac58c1c2651888ef2e9e9b21
commit: d63e63d4210713ddc7eb1b2d2afc4a8d42ccf91e [162/174] ALSA: hdsp: Make uapi/hdsp.h compilable again
config: x86_64-randconfig-s1-20191230 (attached as .config)
compiler: gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
reproduce:
git checkout d63e63d4210713ddc7eb1b2d2afc4a8d42ccf91e
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from <command-line>:1:0:
>> ./usr/include/sound/hdsp.h:35:2: error: unknown type name '__u32'
__u32 input_peaks[26];
^
./usr/include/sound/hdsp.h:36:2: error: unknown type name '__u32'
__u32 playback_peaks[26];
^
./usr/include/sound/hdsp.h:37:2: error: unknown type name '__u32'
__u32 output_peaks[28];
^
>> ./usr/include/sound/hdsp.h:38:2: error: unknown type name '__u64'
__u64 input_rms[26];
^
./usr/include/sound/hdsp.h:39:2: error: unknown type name '__u64'
__u64 playback_rms[26];
^
./usr/include/sound/hdsp.h:41:2: error: unknown type name '__u64'
__u64 output_rms[26];
^
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32167 bytes --]
[-- Attachment #3: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
reply other threads:[~2019-12-30 19:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201912310306.vQMe1dAi%lkp@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=kbuild-all@lists.01.org \
--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