public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, robh+dt@kernel.org, mark.rutland@arm.com,
	ralf@linux-mips.org, paul.burton@mips.com, jhogan@kernel.org,
	agriveaux@deutnet.info, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/4] MIPS: CI20: DTS: Add I2C nodes
Date: Mon, 23 Sep 2019 10:26:44 +0800	[thread overview]
Message-ID: <201909231038.WLeaU93z%lkp@intel.com> (raw)
In-Reply-To: <3f74e79546aff3e2f77e94361685d53f4e44fa7b.1569181001.git.agriveaux@deutnet.info>

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

Hi Alexandre,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[cannot apply to v5.3 next-20190920]
[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/Alexandre-GRIVEAUX/MIPS-CI20-DTS-Add-nodes-to-Creator-CI20-board/20190923-041656
config: mips-allmodconfig (attached as .config)
compiler: mips-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=mips 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> Error: arch/mips/boot/dts/ingenic/ci20.dts:90.1-6 Label or path i2c0 not found
>> Error: arch/mips/boot/dts/ingenic/ci20.dts:168.1-6 Label or path i2c1 not found
>> Error: arch/mips/boot/dts/ingenic/ci20.dts:176.1-6 Label or path i2c2 not found
>> Error: arch/mips/boot/dts/ingenic/ci20.dts:184.1-6 Label or path i2c3 not found
>> Error: arch/mips/boot/dts/ingenic/ci20.dts:192.1-6 Label or path i2c4 not found
   FATAL ERROR: Syntax error parsing input tree

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

  reply	other threads:[~2019-09-23  2:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-22 20:12 [PATCH 0/4] MIPS: CI20: DTS: Add nodes to Creator CI20 board Alexandre GRIVEAUX
2019-09-22 20:12 ` [PATCH 1/4] MIPS: CI20: DTS: Add I2C nodes Alexandre GRIVEAUX
2019-09-23  2:26   ` kbuild test robot [this message]
2019-09-27  4:20     ` Alexandre GRIVEAUX
2019-09-22 20:12 ` [PATCH 2/4] MIPS: CI20: DTS: Add IW8103 Wifi + bluetooth Alexandre GRIVEAUX
2019-09-22 20:12 ` [PATCH 3/4] MIPS: CI20: DTS: Add Leds Alexandre GRIVEAUX
2019-09-22 20:13 ` [PATCH 4/4] MIPS: JZ4780: DTS: Add CPU nodes Alexandre GRIVEAUX

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=201909231038.WLeaU93z%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=agriveaux@deutnet.info \
    --cc=devicetree@vger.kernel.org \
    --cc=jhogan@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=paul.burton@mips.com \
    --cc=ralf@linux-mips.org \
    --cc=robh+dt@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