From: kbuild test robot <lkp@intel.com>
To: Tali Perry <tali.perry1@gmail.com>
Cc: kbuild-all@lists.01.org, robh+dt@kernel.org,
mark.rutland@arm.com, yuenn@google.com, venture@google.com,
benjaminfair@google.com, avifishman70@gmail.com, joel@jms.id.au,
tmaimon77@gmail.com, wsa@the-dreams.de, syniurge@gmail.com,
linux-i2c@vger.kernel.org, openbmc@lists.ozlabs.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Tali Perry <tali.perry1@gmail.com>
Subject: Re: [PATCH v6 2/2] i2c: npcm: Add Nuvoton NPCM I2C controller driver
Date: Thu, 21 Nov 2019 12:55:46 +0800 [thread overview]
Message-ID: <201911211200.tYLwBcQY%lkp@intel.com> (raw)
In-Reply-To: <20191120073622.37938-3-tali.perry1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]
Hi Tali,
I love your patch! Yet something to improve:
[auto build test ERROR on wsa/i2c/for-next]
[also build test ERROR on v5.4-rc8 next-20191120]
[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/Tali-Perry/i2c-npcm-add-NPCM-i2c-controller-driver/20191120-214502
base: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-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=arm
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/i2c/busses/i2c-npcm7xx.c:9:10: fatal error: linux/clk/nuvoton.h: No such file or directory
#include <linux/clk/nuvoton.h>
^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +9 drivers/i2c/busses/i2c-npcm7xx.c
> 9 #include <linux/clk/nuvoton.h>
10 #include <linux/errno.h>
11 #include <linux/i2c.h>
12 #include <linux/interrupt.h>
13 #include <linux/irq.h>
14 #include <linux/kernel.h>
15 #include <linux/mfd/syscon.h>
16 #include <linux/module.h>
17 #include <linux/of.h>
18 #include <linux/platform_device.h>
19 #include <linux/regmap.h>
20 #include <linux/jiffies.h>
21
---
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: 72047 bytes --]
prev parent reply other threads:[~2019-11-21 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 7:36 [PATCH v6 0/2] i2c: npcm: add NPCM i2c controller driver Tali Perry
2019-11-20 7:36 ` [PATCH v6 1/2] dt-bindings: i2c: npcm7xx: add NPCM I2C controller documentation Tali Perry
2019-11-20 7:36 ` [PATCH v6 2/2] i2c: npcm: Add Nuvoton NPCM I2C controller driver Tali Perry
2019-11-21 4:55 ` kbuild test robot [this message]
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=201911211200.tYLwBcQY%lkp@intel.com \
--to=lkp@intel.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=kbuild-all@lists.01.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=syniurge@gmail.com \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=wsa@the-dreams.de \
--cc=yuenn@google.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;
as well as URLs for NNTP newsgroup(s).