mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: James Liao <jamesjj.liao@mediatek.com>
Cc: kbuild-all@01.org, Rob Herring <robh+dt@kernel.org>,
	Russell King <linux@arm.linux.org.uk>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Mike Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
	srv_heupstream@mediatek.com,
	James Liao <jamesjj.liao@mediatek.com>
Subject: Re: [PATCH] arm: dts: mt2701: Add clock controller device nodes
Date: Mon, 28 Mar 2016 16:13:48 +0800	[thread overview]
Message-ID: <201603281638.VIBfNFp6%fengguang.wu@intel.com> (raw)
In-Reply-To: <1459142955-33209-1-git-send-email-jamesjj.liao@mediatek.com>

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

Hi James,

[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.6-rc1 next-20160327]
[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/James-Liao/arm-dts-mt2701-Add-clock-controller-device-nodes/20160328-133113
base:   https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux for-next
config: arm-multi_v7_defconfig (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=arm 

All errors (new ones prefixed by >>):

   In file included from arch/arm/boot/dts/mt2701-evb.dts:16:0:
>> arch/arm/boot/dts/mt2701.dtsi:15:42: fatal error: dt-bindings/clock/mt2701-clk.h: No such file or directory
    #include <dt-bindings/clock/mt2701-clk.h>
                                             ^
   compilation terminated.

vim +15 arch/arm/boot/dts/mt2701.dtsi

     9	 * This program is distributed in the hope that it will be useful,
    10	 * but WITHOUT ANY WARRANTY; without even the implied warranty of
    11	 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    12	 * GNU General Public License for more details.
    13	 */
    14	
  > 15	#include <dt-bindings/clock/mt2701-clk.h>
    16	#include <dt-bindings/interrupt-controller/irq.h>
    17	#include <dt-bindings/interrupt-controller/arm-gic.h>
    18	#include "skeleton64.dtsi"

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

  reply	other threads:[~2016-03-28  8:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28  5:29 James Liao
2016-03-28  8:13 ` kbuild test robot [this message]
2016-03-28  9:47   ` John Crispin

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=201603281638.VIBfNFp6%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jamesjj.liao@mediatek.com \
    --cc=kbuild-all@01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=matthias.bgg@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=srv_heupstream@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

all inboxes | Powered by JetHome®