From: kbuild test robot <lkp@intel.com>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
bgoswami@codeaurora.org, linux-kernel@vger.kernel.org,
plai@codeaurora.org, pierre-louis.bossart@linux.intel.com,
robh+dt@kernel.org, lgirdwood@gmail.com, vkoul@kernel.org,
broonie@kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
kbuild-all@01.org
Subject: Re: [PATCH v3 4/4] ASoC: codecs: add wsa881x amplifier support
Date: Mon, 12 Aug 2019 10:46:34 +0800 [thread overview]
Message-ID: <201908121031.HBxXaLjU%lkp@intel.com> (raw)
In-Reply-To: <20190809133407.25918-5-srinivas.kandagatla@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
Hi Srinivas,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3-rc4 next-20190809]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Srinivas-Kandagatla/ASoC-codecs-Add-WSA881x-Smart-Speaker-amplifier-support/20190812-080612
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 7.4.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
GCC_VERSION=7.4.0 make.cross ARCH=m68k
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> ERROR: "sdw_unregister_driver" [sound/soc/codecs/snd-soc-wsa881x.ko] undefined!
>> ERROR: "sdw_write" [sound/soc/codecs/snd-soc-wsa881x.ko] undefined!
>> ERROR: "__sdw_register_driver" [sound/soc/codecs/snd-soc-wsa881x.ko] undefined!
>> ERROR: "sdw_write" [drivers/base/regmap/regmap-sdw.ko] undefined!
>> ERROR: "sdw_read" [drivers/base/regmap/regmap-sdw.ko] undefined!
---
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: 50926 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2019-08-12 2:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 13:34 [PATCH v3 0/4] ASoC: codecs: Add WSA881x Smart Speaker amplifier support Srinivas Kandagatla
2019-08-09 13:34 ` [PATCH v3 1/4] dt-bindings: soundwire: add slave bindings Srinivas Kandagatla
2019-08-21 9:09 ` Vinod Koul
2019-08-21 21:44 ` Rob Herring
2019-08-22 10:12 ` Srinivas Kandagatla
2019-08-22 11:06 ` Vinod Koul
2019-08-22 12:36 ` Rob Herring
2019-08-22 12:51 ` Vinod Koul
2019-08-22 12:56 ` Srinivas Kandagatla
2019-08-22 16:11 ` Rob Herring
2019-08-09 13:34 ` [PATCH v3 2/4] soundwire: core: add device tree support for slave devices Srinivas Kandagatla
2019-08-09 13:34 ` [PATCH v3 3/4] dt-bindings: ASoC: Add WSA881x bindings Srinivas Kandagatla
2019-08-09 13:34 ` [PATCH v3 4/4] ASoC: codecs: add wsa881x amplifier support Srinivas Kandagatla
2019-08-12 2:46 ` kbuild test robot [this message]
2019-08-12 9:05 ` Srinivas Kandagatla
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=201908121031.HBxXaLjU%lkp@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=plai@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).