From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Chen Zhong <chen.zhong@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Henry Chen <henryc.chen@mediatek.com>,
Steven Liu <steven.liu@mediatek.com>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, John Crispin <blogic@openwrt.org>
Subject: Re: [PATCH V3 2/2] regulator: mt6323: Add support for MT6323 regulator
Date: Mon, 25 Jan 2016 20:48:33 +0800 [thread overview]
Message-ID: <201601252014.ogTG5JRy%fengguang.wu@intel.com> (raw)
In-Reply-To: <1453722989-41622-2-git-send-email-blogic@openwrt.org>
[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]
Hi Chen,
[auto build test ERROR on regulator/for-next]
[also build test ERROR on v4.5-rc1 next-20160125]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/John-Crispin/dt-bindings-regulator-Add-document-for-MT6323-regulator/20160125-184401
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
config: m68k-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=m68k
All errors (new ones prefixed by >>):
>> drivers/regulator/mt6323-regulator.c:20:40: fatal error: linux/mfd/mt6323/registers.h: No such file or directory
#include <linux/mfd/mt6323/registers.h>
^
compilation terminated.
vim +20 drivers/regulator/mt6323-regulator.c
14
15 #include <linux/module.h>
16 #include <linux/of.h>
17 #include <linux/platform_device.h>
18 #include <linux/regmap.h>
19 #include <linux/mfd/mt6397/core.h>
> 20 #include <linux/mfd/mt6323/registers.h>
21 #include <linux/regulator/driver.h>
22 #include <linux/regulator/machine.h>
23 #include <linux/regulator/mt6323-regulator.h>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 35266 bytes --]
next prev parent reply other threads:[~2016-01-25 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 11:56 [PATCH V3 1/2] regulator: Add document for MT6323 regulator John Crispin
2016-01-25 11:56 ` [PATCH V3 2/2] regulator: mt6323: Add support " John Crispin
2016-01-25 12:48 ` kbuild test robot [this message]
[not found] ` <1453722989-41622-2-git-send-email-blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2016-01-26 10:41 ` Paul Bolle
2016-01-26 10:59 ` John Crispin
[not found] ` <1453722989-41622-1-git-send-email-blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2016-01-26 2:31 ` [PATCH V3 1/2] regulator: Add document " Rob Herring
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=201601252014.ogTG5JRy%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=blogic@openwrt.org \
--cc=broonie@kernel.org \
--cc=chen.zhong@mediatek.com \
--cc=henryc.chen@mediatek.com \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=steven.liu@mediatek.com \
/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