From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [Intel-wired-lan] [PATCH 1/3] ASoC: SOF: Introduce descriptors for SOF client
Date: Tue, 12 May 2020 09:17:15 +0800 [thread overview]
Message-ID: <202005120921.BI3Y7pei%lkp@intel.com> (raw)
In-Reply-To: <20200511204146.19176-2-ranjani.sridharan@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]
Hi Ranjani,
I love your patch! Yet something to improve:
[auto build test ERROR on asoc/for-next]
[also build test ERROR on v5.7-rc5 next-20200511]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Ranjani-Sridharan/Virtual-bus-usage-in-the-audio-driver/20200512-050120
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
config: alpha-allyesconfig (attached as .config)
compiler: alpha-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=alpha
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> sound/soc/sof/sof-client.c:17:10: fatal error: linux/virtual_bus.h: No such file or directory
17 | #include <linux/virtual_bus.h>
| ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +17 sound/soc/sof/sof-client.c
7
8 #include <linux/completion.h>
9 #include <linux/debugfs.h>
10 #include <linux/device.h>
11 #include <linux/errno.h>
12 #include <linux/jiffies.h>
13 #include <linux/list.h>
14 #include <linux/mutex.h>
15 #include <linux/module.h>
16 #include <linux/slab.h>
> 17 #include <linux/virtual_bus.h>
18 #include "sof-client.h"
19 #include "sof-priv.h"
20
---
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: 61417 bytes --]
next prev parent reply other threads:[~2020-05-12 1:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 20:41 [Intel-wired-lan] [PATCH 0/3] Virtual bus usage in the audio driver Ranjani Sridharan
2020-05-11 20:41 ` [Intel-wired-lan] [PATCH 1/3] ASoC: SOF: Introduce descriptors for SOF client Ranjani Sridharan
2020-05-12 1:17 ` kbuild test robot [this message]
2020-05-11 20:41 ` [Intel-wired-lan] [PATCH 2/3] ASoC: SOF: Create client driver for IPC test Ranjani Sridharan
2020-05-11 20:41 ` [Intel-wired-lan] [PATCH 3/3] ASoC: SOF: ops: Add new op for client registration Ranjani Sridharan
2020-05-12 2:35 ` kbuild 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=202005120921.BI3Y7pei%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.