From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>,
ARM <linux-arm-kernel@lists.infradead.org>,
Joel Stanley <joel@jms.id.au>, Rob Herring <robh+dt@kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Devicetree Compiler <devicetree-compiler@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Manikandan Elumalai <manikandan.hcl.ers.epl@gmail.com>,
Andrew Jeffery <andrew@aj.id.au>, Vijay Khemka <vkhemka@fb.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: linux-next: build warning after merge of the aspeed tree
Date: Fri, 22 May 2020 10:15:58 +0200 [thread overview]
Message-ID: <CAK8P3a323rPCDDws+us4UYo7ZO6XvkZ13hBChZ40_DwCxBZj_g@mail.gmail.com> (raw)
In-Reply-To: <20200522101638.052bd0a2@canb.auug.org.au>
On Fri, May 22, 2020 at 2:16 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Wed, 20 May 2020 07:56:36 +0000 Joel Stanley <joel@jms.id.au> wrote:
> > On Mon, 11 May 2020 at 15:19, Rob Herring <robh+dt@kernel.org> wrote:
> > > On Wed, 6 May 2020 at 23:13, Joel Stanley <joel@jms.id.au> wrote:
> > > > > These are IPMB nodes with the SLAVE_ADDRESS bit set:
> > > > >
> > > > > +&i2c5 {
> > > > > + //Host3 IPMB bus
> > > > > + status = "okay";
> > > > > + multi-master;
> > > > > + ipmb5@10 {
> > > > > + compatible = "ipmb-dev";
> > > > > + reg = <(0x10 | I2C_OWN_SLAVE_ADDRESS)>;
> > > > > + i2c-protocol;
> > > > > + };
> > > > >
> > > > > This is a correct entry, so dtc should not warn about it.
> > > >
> > > > I sent a patch for dtc here:
> > > > https://lore.kernel.org/lkml/20200508063904.60162-1-joel@jms.id.au/
> > >
> > > Patches for dtc need to be against upstream dtc. There's already a
> > > similar patch posted for it which I commented on and never saw a
> > > respin.
> >
> > Can I suggest some instructions in scsripts/dtc explaining that you
> > don't take patches in the kernel tree for this code?
> >
> > I've sent the patch so it applies to the dtc tree. It would be good to
> > see that change propagate over to -next as others have reported this
> > warning.
>
> These warnings now appear in the arm-soc tree.
Right, I also saw them earlier.
Joel, have you sent your patch to David Gibson for integration into
upstream dtc?
I don't know who sent the other patch, but as long as one of them
gets merged, I'd hope we can pull that into kernel as well.
Arnd
next prev parent reply other threads:[~2020-05-22 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200507091008.1bd38185@canb.auug.org.au>
[not found] ` <20200507091008.1bd38185-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2020-05-06 23:13 ` linux-next: build warning after merge of the aspeed tree Joel Stanley
2020-05-08 6:40 ` Joel Stanley
[not found] ` <CACPK8XcUydETZvJEkWPvLnLXatAg3D-MfA1yeDzE0epc-hisJQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-05-11 15:19 ` Rob Herring
2020-05-20 7:56 ` Joel Stanley
2020-05-22 0:16 ` Stephen Rothwell
2020-05-22 8:15 ` Arnd Bergmann [this message]
[not found] ` <CAK8P3a323rPCDDws+us4UYo7ZO6XvkZ13hBChZ40_DwCxBZj_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-05-28 6:09 ` Joel Stanley
2020-05-28 7:21 ` 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=CAK8P3a323rPCDDws+us4UYo7ZO6XvkZ13hBChZ40_DwCxBZj_g@mail.gmail.com \
--to=arnd@arndb.de \
--cc=andrew@aj.id.au \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=manikandan.hcl.ers.epl@gmail.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vkhemka@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).