From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: mt8173.dtsi: correct i2c node names
Date: Sun, 27 Sep 2015 15:00:57 +0200 [thread overview]
Message-ID: <5607E889.2060501@gmail.com> (raw)
In-Reply-To: <CAGS+omCzycc+RFeDftooDcj_f9M4SXhoO79u8m9e=ZiL1QV1tA@mail.gmail.com>
On 16/09/15 15:34, Daniel Kurtz wrote:
> On Wed, Sep 16, 2015 at 9:35 AM, Yingjoe Chen <yingjoe.chen@mediatek.com> wrote:
>> Node name in device tree should describe general class of the
>> device. Correct incorrect i2c node names.
>>
>> Signed-off-by: Yingjoe Chen <yingjoe.chen@mediatek.com>
>
> Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
>
Applied, thanks.
>> ---
>> This is based on v4.3-rc1.
>> All the other i2c node names are correct.
>> ---
>> arch/arm64/boot/dts/mediatek/mt8173.dtsi | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
>> index d18ee42..7f360b7 100644
>> --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
>> +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
>> @@ -365,7 +365,7 @@
>> status = "disabled";
>> };
>>
>> - i2c3: i2c3 at 11010000 {
>> + i2c3: i2c at 11010000 {
>> compatible = "mediatek,mt8173-i2c";
>> reg = <0 0x11010000 0 0x70>,
>> <0 0x11000280 0 0x80>;
>> @@ -381,7 +381,7 @@
>> status = "disabled";
>> };
>>
>> - i2c4: i2c4 at 11011000 {
>> + i2c4: i2c at 11011000 {
>> compatible = "mediatek,mt8173-i2c";
>> reg = <0 0x11011000 0 0x70>,
>> <0 0x11000300 0 0x80>;
>> @@ -397,7 +397,7 @@
>> status = "disabled";
>> };
>>
>> - i2c6: i2c6 at 11013000 {
>> + i2c6: i2c at 11013000 {
>> compatible = "mediatek,mt8173-i2c";
>> reg = <0 0x11013000 0 0x70>,
>> <0 0x11000080 0 0x80>;
>> --
>> 1.9.1
>>
prev parent reply other threads:[~2015-09-27 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 1:35 [PATCH] arm64: mt8173.dtsi: correct i2c node names Yingjoe Chen
2015-09-16 13:34 ` Daniel Kurtz
2015-09-27 13:00 ` Matthias Brugger [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=5607E889.2060501@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).