From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Rob Herring <robh@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: marvell: kirkwood: Fix at24 EEPROM node name
Date: Mon, 04 Nov 2024 17:05:34 +0100 [thread overview]
Message-ID: <878qtz9e7l.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <CAL_JsqLLRSEaDv=Zm_LQH9cpgH2prh21+cmovgSR=pzQTuRtZQ@mail.gmail.com>
Hello Rob,
> On Tue, Sep 10, 2024 at 4:59 PM Rob Herring (Arm) <robh@kernel.org> wrote:
>>
>> at24.yaml defines the node name for at24 EEPROMs as 'eeprom'.
>>
>> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
>> ---
>> arch/arm/boot/dts/marvell/kirkwood-openblocks_a7.dts | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Ping!
>
> Are Marvell platforms still maintained?
Actually I just applied it this morning, and was about to notify about
it.
Applied on mvebu/dt
Thanks,
Gregory
>
>>
>> diff --git a/arch/arm/boot/dts/marvell/kirkwood-openblocks_a7.dts b/arch/arm/boot/dts/marvell/kirkwood-openblocks_a7.dts
>> index 9c438f10f737..2bc4b68bd723 100644
>> --- a/arch/arm/boot/dts/marvell/kirkwood-openblocks_a7.dts
>> +++ b/arch/arm/boot/dts/marvell/kirkwood-openblocks_a7.dts
>> @@ -44,7 +44,7 @@ sata@80000 {
>> i2c@11100 {
>> status = "okay";
>>
>> - s24c02: s24c02@50 {
>> + s24c02: eeprom@50 {
>> compatible = "atmel,24c02";
>> reg = <0x50>;
>> };
>> --
>> 2.45.2
>>
--
Grégory CLEMENT, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-11-04 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 21:59 [PATCH] ARM: dts: marvell: kirkwood: Fix at24 EEPROM node name Rob Herring (Arm)
2024-09-10 22:20 ` Andrew Lunn
2024-11-04 13:24 ` Rob Herring
2024-11-04 14:07 ` Andrew Lunn
2024-11-04 16:05 ` Gregory CLEMENT [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=878qtz9e7l.fsf@BLaptop.bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.