linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vijay Khemka <vijaykhemka@fb.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Joel Stanley <joel@jms.id.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>
Subject: Re: linux-next: build failure after merge of the aspeed tree
Date: Tue, 11 Feb 2020 00:48:22 +0000	[thread overview]
Message-ID: <46287780-32D0-46D3-9604-D71BA190821E@fb.com> (raw)
In-Reply-To: <20200211084449.05e3b3cb@canb.auug.org.au>

Hi Joel,
I am looking into fixing warning for my patch. If you have any idea or suggestions, please advice.

Regards
-Vijay

On 2/10/20, 1:45 PM, "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)
    
    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
    


  parent reply	other threads:[~2020-02-11  0:48 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
2020-02-11  0:48 ` Vijay Khemka [this message]
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=46287780-32D0-46D3-9604-D71BA190821E@fb.com \
    --to=vijaykhemka@fb.com \
    --cc=eajames@linux.ibm.com \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).