From: Tony Lindgren Subject: Re: [PATCH] ARM: dts: Configure omap5 AESS Date: Thu, 16 Jan 2020 10:52:17 -0800 Message-ID: <20200116185217.GU5885@atomide.com> References: <20200114150937.18304-1-tony@atomide.com> <202001162346.4yVlrA8l%lkp@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <202001162346.4yVlrA8l%lkp-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: kbuild test robot Cc: kbuild-all-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org, linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, =?utf-8?Q?Beno=C3=AEt?= Cousson , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "H . Nikolaus Schaller" , Matthijs van Duin , Peter Ujfalusi , Tero Kristo List-Id: linux-omap@vger.kernel.org * kbuild test robot [200116 15:55]: > Hi Tony, > > I love your patch! Yet something to improve: > > [auto build test ERROR on robh/for-next] > [also build test ERROR on omap/for-next balbi-usb/next v5.5-rc6 next-20200115] > [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/Tony-Lindgren/ARM-dts-Configure-omap5-AESS/20200115-114737 > base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next > config: arm-defconfig (attached as .config) > compiler: arm-linux-gnueabi-gcc (GCC) 7.5.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.5.0 make.cross ARCH=arm > > If you fix the issue, kindly add following tag > Reported-by: kbuild test robot > > All errors (new ones prefixed by >>): > > >> Error: arch/arm/boot/dts/omap5-l4-abe.dtsi:447.27-28 syntax error > FATAL ERROR: Unable to parse input tree This patch has a dependency to a clock related patch as described in the original patch email so this error can be ignored. Regards, Tony