mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: kbuild-all@01.org, Geert Uytterhoeven <geert@linux-m68k.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Jacopo Mondi <jacopo@jmondi.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Simon Horman <horms@verge.net.au>,
	linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Phil Edworthy <phil.edworthy@renesas.com>
Subject: Re: [PATCH v2 3/3] ARM: dts: r9a06g032: Add pinctrl node
Date: Fri, 31 Aug 2018 08:50:49 +0800	[thread overview]
Message-ID: <201808310827.o3GAs37i%fengguang.wu@intel.com> (raw)
In-Reply-To: <1535634775-19365-4-git-send-email-phil.edworthy@renesas.com>

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

Hi Phil,

Thank you for the patch! Yet something to improve:

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

url:    https://github.com/0day-ci/linux/commits/Phil-Edworthy/Renesas-R9A06G032-PINCTRL-Driver/20180831-050708
base:   https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
config: arm-mvebu_v5_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.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.2.0 make.cross ARCH=arm 

All errors (new ones prefixed by >>):

>> Error: arch/arm/boot/dts/r9a06g032.dtsi:93.23-24 syntax error
   FATAL ERROR: Unable to parse 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: 23513 bytes --]

  reply	other threads:[~2018-08-31  0:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 13:12 [PATCH v2 0/3] Renesas R9A06G032 PINCTRL Driver Phil Edworthy
2018-08-30 13:12 ` [PATCH v2 1/3] dt-bindings: pinctrl: renesas,rzn1-pinctrl: documentation Phil Edworthy
2018-08-30 13:12 ` [PATCH v2 2/3] pinctrl: renesas: Renesas RZ/N1 pinctrl driver Phil Edworthy
2018-08-30 13:12 ` [PATCH v2 3/3] ARM: dts: r9a06g032: Add pinctrl node Phil Edworthy
2018-08-31  0:50   ` kbuild test robot [this message]
2018-08-31  8:13     ` Phil Edworthy
2018-09-06  9:36       ` Simon Horman
2018-09-03 10:33 ` [PATCH v2 0/3] Renesas R9A06G032 PINCTRL Driver jacopo mondi
2018-09-03 11:03   ` Phil Edworthy
2018-09-03 11:25     ` jacopo mondi
2018-09-10  7:45       ` Linus Walleij
2018-09-05  9:36     ` Geert Uytterhoeven
2018-09-05  9:58       ` Phil Edworthy
2018-09-10  7:48         ` Linus Walleij
2018-09-10  9:42           ` Geert Uytterhoeven
2018-09-10  9:54             ` Phil Edworthy
2018-09-10  9:58               ` Geert Uytterhoeven
2018-09-10  9:46           ` Laurent Pinchart

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=201808310827.o3GAs37i%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=jacopo@jmondi.org \
    --cc=kbuild-all@01.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=phil.edworthy@renesas.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®