From: kbuild test robot <lkp@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: [tip:WIP.core/toplevel 4/6] drivers/sound/soc/intel/skylake/skl-sst-ipc.c:14:10: fatal error: drivers/sound/hdaudio_ext.h: No such file or directory
Date: Tue, 24 Sep 2019 06:52:33 +0800 [thread overview]
Message-ID: <201909240632.pKsncIt7%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/tip/tip.git WIP.core/toplevel
head: 166a63584297d3e1e1d7d380ee13dfe1a871ab04
commit: 7eff58ad913615232613491bec0f54d34ce73bda [4/6] toplevel: Fix up drivers/sound/ movement effects
config: x86_64-rhel-7.6 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
reproduce:
git checkout 7eff58ad913615232613491bec0f54d34ce73bda
# 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 >>):
>> drivers/sound/soc/intel/skylake/skl-sst-ipc.c:14:10: fatal error: drivers/sound/hdaudio_ext.h: No such file or directory
#include "drivers/sound/hdaudio_ext.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +14 drivers/sound/soc/intel/skylake/skl-sst-ipc.c
8
9 #include "../common/sst-dsp.h"
10 #include "../common/sst-dsp-priv.h"
11 #include "skl.h"
12 #include "skl-sst-dsp.h"
13 #include "skl-sst-ipc.h"
> 14 #include "drivers/sound/hdaudio_ext.h"
15
16
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 48279 bytes --]
reply other threads:[~2019-09-23 22:53 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=201909240632.pKsncIt7%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®