All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Eddie James <eajames@linux.ibm.com>,
	Vijay Khemka <vijaykhemka@fb.com>
Subject: Re: linux-next: build failure after merge of the aspeed tree
Date: Mon, 10 Feb 2020 22:17:18 +0000	[thread overview]
Message-ID: <CACPK8XfGKox38H1XQaGKUDe5y2hV06+WSmtJDNz4zLtE7k9ZjA@mail.gmail.com> (raw)
In-Reply-To: <20200211084449.05e3b3cb@canb.auug.org.au>

On Mon, 10 Feb 2020 at 21:45, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the aspeed tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> arch/arm/boot/dts/aspeed-g6.dtsi:322.35-327.7: ERROR (duplicate_node_names): /ahb/apb/syscon@1e6e2000/interrupt-controller: Duplicate node name
> ERROR: Input tree has errors, aborting (use -f to force output)

Thanks for the report Stephen. I've dropped the offending commit and
re-pushed. We should be good for tomorrow's next.

Cheers,

Joel

>
> Caused by commit
>
>   091ff5206ef3 ("ARM: dts: aspeed: ast2600: Fix SCU IRQ controller node addresses")
>
> Also these warnings:
>
> arch/arm/boot/dts/aspeed-bmc-facebook-tiogapass.dts:435.11-439.4: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@140/ipmb0@10: I2C bus unit address format error, expected "40000010"
> arch/arm/boot/dts/aspeed-bmc-facebook-tiogapass.dts:437.3-30: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@140/ipmb0@10:reg: I2C address must be less than 10-bits, got "0x40000010"
> arch/arm/boot/dts/aspeed-bmc-facebook-tiogapass.dts:521.11-525.4: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@380/ipmb0@10: I2C bus unit address format error, expected "40000010"
> arch/arm/boot/dts/aspeed-bmc-facebook-tiogapass.dts:523.3-30: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@380/ipmb0@10:reg: I2C address must be less than 10-bits, got "0x40000010"
>
> Caused by commit
>
>   a59b1792adf1 ("ARM: dts: aspeed: tiogapass: Add IPMB device")
>
> I have used the aspeed tree from next-20200210 for today.
>
> --
> Cheers,
> Stephen Rothwell

  reply	other threads:[~2020-02-10 22:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 21:44 linux-next: build failure after merge of the aspeed tree Stephen Rothwell
2020-02-10 22:17 ` Joel Stanley [this message]
2020-02-11  0:48 ` Vijay Khemka
2020-02-11  1:33 ` Vijay Khemka
2023-12-12 22:30 Stephen Rothwell
2023-12-13 22:06 ` Joel Stanley

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=CACPK8XfGKox38H1XQaGKUDe5y2hV06+WSmtJDNz4zLtE7k9ZjA@mail.gmail.com \
    --to=joel@jms.id.au \
    --cc=eajames@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vijaykhemka@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.