public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	"magnus.damm" <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 0/4] arm64: dts: renesas: Fix PHY C22 compatible strings
Date: Thu, 26 Mar 2026 05:58:43 +0100	[thread overview]
Message-ID: <32a1ea50-fca3-4eed-996f-e28be1908770@mailbox.org> (raw)
In-Reply-To: <CAMuHMdV_rGpnx6DzmdDgAsRJ4hXy8TP+pSnnzURjeGZfxB+5wg@mail.gmail.com>

On 3/25/26 3:32 PM, Geert Uytterhoeven wrote:

Hello Geert,

> On Mon, 16 Mar 2026 at 13:37, Marek Vasut <marek.vasut@mailbox.org> wrote:
>> On 3/16/26 10:11 AM, Biju Das wrote:
>>>> There is also Marek's older series ([1][2], as Marek doesn't do cover letters ;-).
>>
>> You seem to be commenting on a 0/4 cover letter here ...
> 
> Ha, the exception to the general rule ;-)

Hehehe.

>>>> [1] "[PATCH 1/2] ARM: dts: renesas: Drop ethernet-phy-ieee802.3-c22 from PHY compatible string on all
>>>> RZ boards"
>>>>       https://lore.kernel.org/20240630034649.173229-1-marex@denx.de/
>>>> [2] "[PATCH 2/2] arm64: dts: renesas: Drop ethernet-phy-ieee802.3-c22 from PHY compatible string on
>>>> all RZ boards"
>>>>       https://lore.kernel.org/20240630034649.173229-2-marex@denx.de
>>>
>>> I haven't seen these patches.
>>
>> They are deprecated.
>>
>>> It does not cover all the SoCs/boards. If Marek want to take over, He can send next version
>>> covering all Renesas boards + binding change.
>> Isn't this series effectively exactly that ?
> 
> I believe we still have e.g. the KSZ8041 and KSZ9031 PHY nodes to fix,
> for both RZ and R-Car boards? Some of them were covered by [1] and
> [2] above.

I hope this is now all addressed by two board fixes [3] [4] and one 
larger fix [5]. But there are also other warnings on the arm32 side 
which are not related to ethernet schemas.

[3] 
https://lore.kernel.org/linux-arm-kernel/20260326045355.223529-1-marek.vasut+renesas@mailbox.org/
[4] 
https://lore.kernel.org/linux-arm-kernel/20260326045416.223556-1-marek.vasut+renesas@mailbox.org/
[5] 
https://lore.kernel.org/linux-arm-kernel/20260326045523.223620-1-marek.vasut+renesas@mailbox.org/

-- 
Best regards,
Marek Vasut


      reply	other threads:[~2026-03-26  4:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 16:39 [PATCH 0/4] arm64: dts: renesas: Fix PHY C22 compatible strings Marek Vasut
2026-03-13 16:39 ` [PATCH 1/4] arm64: dts: renesas: Drop RTL8211E PHY C22 compatible string Marek Vasut
2026-03-25 14:22   ` Geert Uytterhoeven
2026-03-13 16:39 ` [PATCH 2/4] arm64: dts: renesas: Drop RTL8211F " Marek Vasut
2026-03-25 14:23   ` Geert Uytterhoeven
2026-03-13 16:39 ` [PATCH 3/4] arm64: dts: renesas: Drop KSZ9131 " Marek Vasut
2026-03-25 14:23   ` Geert Uytterhoeven
2026-03-13 16:39 ` [PATCH 4/4] arm64: dts: renesas: Fix KSZ9131 PHY bogus txdv-skew-psec property Marek Vasut
2026-03-13 17:16   ` Biju Das
2026-03-25 14:29   ` Geert Uytterhoeven
2026-03-13 16:52 ` [PATCH 0/4] arm64: dts: renesas: Fix PHY C22 compatible strings Biju Das
2026-03-13 17:18   ` Marek Vasut
2026-03-16  8:57   ` Geert Uytterhoeven
2026-03-16  9:11     ` Biju Das
2026-03-16 12:37       ` Marek Vasut
2026-03-16 12:58         ` Biju Das
2026-03-16 15:06           ` Marek Vasut
2026-03-16 15:12             ` Biju Das
2026-03-25 14:32         ` Geert Uytterhoeven
2026-03-26  4:58           ` Marek Vasut [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=32a1ea50-fca3-4eed-996f-e28be1908770@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --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