public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: kbuild-all@01.org, swarren@wwwdotorg.org,
	thierry.reding@gmail.com, robh+dt@kernel.org, pawel.moll@arm.com,
	mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
	galak@codeaurora.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: [PATCH 2/2] arm64: tegra: Jetson-TX1: Add DT entry for system PMIC MAX77620
Date: Sun, 6 Mar 2016 18:51:19 +0800	[thread overview]
Message-ID: <201603061816.5RCjo7Lz%fengguang.wu@intel.com> (raw)
In-Reply-To: <1456751211-14341-2-git-send-email-ldewangan@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]

Hi Laxman,

[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.5-rc6 next-20160304]
[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/Laxman-Dewangan/arm64-tegra-Add-DT-entry-for-keys-used-in-Jetson-TX1/20160229-212214
base:   https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux for-next
config: arm64-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=arm64 

All errors (new ones prefixed by >>):

>> arch/arm64/boot/dts/nvidia/tegra210-p2371-2180.dts:5:38: fatal error: dt-bindings/mfd/max77620.h: No such file or directory
    #include <dt-bindings/mfd/max77620.h>
                                         ^
   compilation terminated.

vim +5 arch/arm64/boot/dts/nvidia/tegra210-p2371-2180.dts

     1	/dts-v1/;
     2	
     3	#include "tegra210-p2180.dtsi"
     4	#include "tegra210-p2597.dtsi"
   > 5	#include <dt-bindings/mfd/max77620.h>
     6	#include <dt-bindings/input/input.h>
     7	
     8	/ {

---
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: 48281 bytes --]

  reply	other threads:[~2016-03-06 10:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 13:06 [PATCH 1/2] arm64: tegra: Add DT entry for keys used in Jetson-TX1 Laxman Dewangan
2016-02-29 13:06 ` [PATCH 2/2] arm64: tegra: Jetson-TX1: Add DT entry for system PMIC MAX77620 Laxman Dewangan
2016-03-06 10:51   ` kbuild test robot [this message]
2016-03-01 14:28 ` [PATCH 1/2] arm64: tegra: Add DT entry for keys used in Jetson-TX1 Thierry Reding

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=201603061816.5RCjo7Lz%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kbuild-all@01.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.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