From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Shawn Guo <shawnguo@kernel•org>
Cc: Alison Wang <alison.wang@nxp•com>,
Changming Huang <jerry.huang@nxp•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warning after merge of the imx-mxs tree
Date: Tue, 26 Apr 2022 10:06:59 +1000 [thread overview]
Message-ID: <20220426100659.0e3f3ca8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Hi all,
After merging the imx-mxs tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
arch/arm/boot/dts/ls1021a-iot.dts:150.3-26: Warning (clocks_property): /soc/i2c@2180000/audio-codec@2a:clocks: cell 1 is not a phandle reference
arch/arm/boot/dts/ls1021a-iot.dts:144.27-151.4: Warning (clocks_property): /soc/i2c@2180000/audio-codec@2a: Missing property '#clock-cells' in node /soc/interrupt-controller@1400000 or bad phandle (referred from clocks[1])
Introduced by commit
23f550d5f7f6 ("ARM: dts: Add initial LS1021A IoT board dts support")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-04-26 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 0:06 Stephen Rothwell [this message]
2022-04-26 1:15 ` linux-next: build warning after merge of the imx-mxs tree Shawn Guo
-- strict thread matches above, loose matches on Subject: below --
2018-05-13 23:21 Stephen Rothwell
2018-05-14 0:56 ` Shawn Guo
2018-05-14 13:05 ` Rob Herring
2018-05-14 13:42 ` Shawn Guo
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=20220426100659.0e3f3ca8@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alison.wang@nxp$(echo .)com \
--cc=jerry.huang@nxp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=shawnguo@kernel$(echo .)org \
/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