From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Cooper <jason@lakedaemon•net>, Andrew Lunn <andrew@lunn•ch>,
Gregory Clement <gregory.clement@bootlin•com>,
ARM <linux-arm-kernel@lists•infradead.org>
Cc: Aryan Srivastava <aryan.srivastava@alliedtelesis•co.nz>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Olof Johansson <olof@lixom•net>, Arnd Bergmann <arnd@arndb•de>
Subject: Re: linux-next: build warning after merge of the mvebu tree
Date: Fri, 9 Apr 2021 09:24:17 +1000 [thread overview]
Message-ID: <20210409092417.36b22630@canb.auug.org.au> (raw)
In-Reply-To: <20210408095612.71e8c56e@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
Hi all,
On Thu, 8 Apr 2021 09:56:12 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the mvebu tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> arch/arm/boot/dts/armada-385-atl-x530.dts:171.14-199.4: Warning (spi_bus_reg): /soc/spi@10680/spi-flash@0: SPI bus unit address format error, expected "1"
>
> Introduced by commit
>
> c6dfc019c239 ("ARM: dts: mvebu: Add device tree for ATL-x530 Board")
This is now a warning after the merge of the arm-soc tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-04-08 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 23:56 linux-next: build warning after merge of the mvebu tree Stephen Rothwell
2021-04-08 23:24 ` Stephen Rothwell [this message]
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=20210409092417.36b22630@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andrew@lunn$(echo .)ch \
--cc=arnd@arndb$(echo .)de \
--cc=aryan.srivastava@alliedtelesis$(echo .)co.nz \
--cc=gregory.clement@bootlin$(echo .)com \
--cc=jason@lakedaemon$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=olof@lixom$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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