From: santosh.shilimkar@oracle.com (santosh.shilimkar at oracle.com)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: build failure after merge of the keystone tree
Date: Sun, 22 Oct 2017 20:23:19 -0700 [thread overview]
Message-ID: <3ed1f18a-204c-961a-9d81-b36e00d4aaf5@oracle.com> (raw)
In-Reply-To: <20171010071924.ddxkylkwq44qh47q@sirena.co.uk>
On 10/10/17 12:19 AM, Mark Brown wrote:
> Hi Santosh,
>
> After merging the keystone tree, today's linux-next build
> (multi_v7_defconfig) failed like this:
>
> DTC arch/arm/boot/dts/keystone-k2g-evm.dtb
> Error: /home/broonie/tmpfs/next/arch/arm/boot/dts/keystone-k2g-evm.dts:150.1-15 syntax error
> FATAL ERROR: Unable to parse input tree
> scripts/Makefile.lib:316: recipe for target 'arch/arm/boot/dts/keystone-k2g-evm.dtb' failed
> make[2]: *** [arch/arm/boot/dts/keystone-k2g-evm.dtb] Error 1
>
> Caused by commit
>
> a6f244505915f ("ARM: dts: keystone-k2g-evm: Add I2C EEPROM DT entry")
>
> I've used the keystone tree from yesterday.
>
I fixed this next day but forgot to reply to you Mark.
Regards,
Santosh
next prev parent reply other threads:[~2017-10-23 3:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 7:19 linux-next: build failure after merge of the keystone tree Mark Brown
2017-10-23 3:23 ` santosh.shilimkar at oracle.com [this message]
2017-10-23 8:33 ` Mark Brown
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=3ed1f18a-204c-961a-9d81-b36e00d4aaf5@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=linux-arm-kernel@lists.infradead.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).