From: kbuild test robot <lkp@intel.com>
To: Sandeep Maheswaram <sanm@codeaurora.org>
Cc: kbuild-all@lists.01.org, linux-usb@vger.kernel.org,
linux-omap@vger.kernel.org, Felipe Balbi <balbi@kernel.org>,
Stephen Boyd <swboyd@chromium.org>
Subject: [balbi-usb:testing/next 86/89] Error: arch/arm64/boot/dts/qcom/sc7180.dtsi:1450.33-34 syntax error
Date: Sat, 16 May 2020 19:17:22 +0800 [thread overview]
Message-ID: <202005161919.jGPYtmmG%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git testing/next
head: a65a1ec70639afa5ff7990cf33213dd41f3c7176
commit: d0bae79b5856aaec5096730bb0970b04d49defae [86/89] arm64: dts: qcom: sc7180: Add interconnect properties for USB
config: arm64-randconfig-r003-20200515 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout d0bae79b5856aaec5096730bb0970b04d49defae
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> Error: arch/arm64/boot/dts/qcom/sc7180.dtsi:1450.33-34 syntax error
FATAL ERROR: Unable to parse input tree
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 39290 bytes --]
reply other threads:[~2020-05-16 11:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202005161919.jGPYtmmG%lkp@intel.com \
--to=lkp@intel.com \
--cc=balbi@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sanm@codeaurora.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).