From: Shawn Guo <shawnguo@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Li Yang <leoyang.li@nxp.com>
Subject: Re: [PATCH] arm64: dts: fsl: Fix I2C and SPI bus warnings
Date: Wed, 26 Sep 2018 17:09:18 +0800 [thread overview]
Message-ID: <20180926090916.GC26692@dragon> (raw)
In-Reply-To: <20180913181245.25484-19-robh@kernel.org>
On Thu, Sep 13, 2018 at 01:12:43PM -0500, Rob Herring wrote:
> dtc has new checks for I2C and SPI buses. Fix the SPI bus node names
> and warnings in unit-addresses.
>
> arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dtb: Warning (i2c_bus_reg): /soc/i2c@2180000/eeprom@57: I2C bus unit address format error, expected "53"
> arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dtb: Warning (i2c_bus_reg): /soc/i2c@2180000/eeprom@56: I2C bus unit address format error, expected "52"
>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: Li Yang <leoyang.li@nxp.com>
> Signed-off-by: Rob Herring <robh@kernel.org>
Applied, thanks.
prev parent reply other threads:[~2018-09-26 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 18:12 [PATCH] arm64: dts: fsl: Fix I2C and SPI bus warnings Rob Herring
2018-09-13 18:19 ` Li Yang
2018-09-26 9:09 ` Shawn Guo [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=20180926090916.GC26692@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.org \
/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).