LKML Archive on
help / color / mirror / Atom feed
From: kbuild test robot <>
To: Philippe Cornu <>
Cc:, Rob Herring <>,
	Mark Rutland <>,
	Russell King <>,
	Maxime Coquelin <>,
	Alexandre Torgue <>,,,,
	Benjamin Gaignard <>,
	Yannick Fertre <>,
	Philippe Cornu <>,
	Vincent Abriou <>
Subject: Re: [PATCH 3/3] ARM: dts: stm32: Add display support on stm32f469-disco
Date: Sun, 18 Feb 2018 06:58:04 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

Hi Philippe,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.16-rc1 next-20180216]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

base: for-next
config: arm-at91_dt_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
        wget -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 >>):

>> Error: arch/arm/boot/dts/stm32f469.dtsi:14.21-22 syntax error
   FATAL ERROR: Unable to parse input tree

0-DAY kernel test infrastructure                Open Source Technology Center                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 23600 bytes --]

  reply	other threads:[~2018-02-17 22:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15  8:20 [PATCH 0/3] ARM: dts: stm32: Add display support on stm32f469-disco Philippe Cornu
2018-02-15  8:20 ` [PATCH 1/3] ARM: dts: stm32: Add dt-bindings gpio.h include " Philippe Cornu
2018-02-15  8:20 ` [PATCH 2/3] ARM: dts: stm32: Add new stm32f469 dtsi file with mipi dsi Philippe Cornu
2018-02-15  8:20 ` [PATCH 3/3] ARM: dts: stm32: Add display support on stm32f469-disco Philippe Cornu
2018-02-17 22:58   ` kbuild test robot [this message]
2018-05-03 14:58 ` [PATCH 0/3] " Alexandre Torgue

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).