From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: kbuild test robot <fengguang.wu@intel.com>,
Thomas Abraham <thomas.ab@samsung.com>
Cc: kbuild-all@01.org, Kukjin Kim <kgene@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Javier Martinez Canillas <javier@dowhile0.org>
Subject: Re: [linux-next:master 3331/3796] Error: arch/arm/boot/dts/exynos5250.dtsi:65.21-22 syntax error
Date: Thu, 23 Jul 2015 09:29:57 +0900 [thread overview]
Message-ID: <55B03585.7020703@samsung.com> (raw)
In-Reply-To: <201507222329.EDXw3ZRS%fengguang.wu@intel.com>
On 23.07.2015 00:00, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 72a68fd733c8b6cd2e0ebc0586a9103067cd4ed7
> commit: 565872a601c4d91a75b917b1fb40ff27ad7ebb08 [3331/3796] ARM: dts: add CPU OPP and regulator supply property for exynos5250
> config: arm-exynos_defconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 565872a601c4d91a75b917b1fb40ff27ad7ebb08
> # save the attached .config to linux build tree
> make.cross ARCH=arm
>
> Note: the linux-next/master HEAD 72a68fd733c8b6cd2e0ebc0586a9103067cd4ed7 builds fine.
> It may have been fixed somewhere.
>
> All error/warnings (new ones prefixed by >>):
>
>>> Error: arch/arm/boot/dts/exynos5250.dtsi:65.21-22 syntax error
> FATAL ERROR: Unable to parse input tree
I reported this to Kukjin already, after he released the non-bisectable
branches. Unfortunately no response...
Dear Kukjin,
Are you going to fix your branches?
Best regards,
Krzysztof
parent reply other threads:[~2015-07-23 0:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201507222329.EDXw3ZRS%fengguang.wu@intel.com>]
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=55B03585.7020703@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=fengguang.wu@intel.com \
--cc=javier@dowhile0.org \
--cc=kbuild-all@01.org \
--cc=kgene@kernel.org \
--cc=thomas.ab@samsung.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