From: Krzysztof Kozlowski <krzk@kernel.org>
To: Robert Marko <robert.marko@sartura.hr>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
claudiu.beznea@tuxon.dev, Steen.Hegelund@microchip.com,
daniel.machon@microchip.com, UNGLinuxDriver@microchip.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
vkoul@kernel.org, linux@roeck-us.net, andi.shyti@kernel.org,
lee@kernel.org, andrew+netdev@lunn.ch, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linusw@kernel.org,
olivia@selenic.com, radu_nicolae.pirea@upb.ro,
richard.genoud@bootlin.com, gregkh@linuxfoundation.org,
jirislaby@kernel.org, mturquette@baylibre.com, sboyd@kernel.org,
richardcochran@gmail.com, wsa+renesas@sang-engineering.com,
romain.sioen@microchip.com, Ryan.Wanner@microchip.com,
lars.povlsen@microchip.com, tudor.ambarus@linaro.org,
charan.pedumuru@microchip.com, kavyasree.kotagiri@microchip.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
dmaengine@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-i2c@vger.kernel.org, netdev@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-spi@vger.kernel.org,
linux-serial@vger.kernel.org, linux-usb@vger.kernel.org,
linux-clk@vger.kernel.org, mwalle@kernel.org,
luka.perkov@sartura.hr
Subject: Re: [PATCH v2 05/19] dt-bindings: arm: microchip: move SparX-5 to generic Microchip binding
Date: Wed, 17 Dec 2025 14:23:12 +0100 [thread overview]
Message-ID: <3d6f254c-d53f-47d9-8081-8506d202bf9d@kernel.org> (raw)
In-Reply-To: <CA+HBbNGNMGRL11kdg14LwkiTazXJYXOZeVCKsmW6-XF6k5+sVA@mail.gmail.com>
On 16/12/2025 18:01, Robert Marko wrote:
> On Tue, Dec 16, 2025 at 4:58 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On 15/12/2025 17:35, Robert Marko wrote:
>>> Now that we have a generic Microchip binding, lets move SparX-5 as well as
>>> there is no reason to have specific binding file for each SoC series.
>>>
>>> The check for AXI node was dropped.
>>
>> Why?
>
> According to Conor, it is pointless [1]
You have entire commit msg to explain this. It's basically my third
question where reasoning behind changes is not explained.
When you send v3, you will get the same questions...
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-17 13:23 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 16:35 [PATCH v2 01/19] include: dt-bindings: add LAN969x clock bindings Robert Marko
2025-12-15 16:35 ` [PATCH v2 02/19] dt-bindings: usb: Add Microchip LAN969x support Robert Marko
2025-12-15 16:35 ` [PATCH v2 03/19] dt-bindings: arm: AT91: relicense to dual GPL-2.0/BSD-2-Clause Robert Marko
2025-12-16 15:54 ` Krzysztof Kozlowski
2025-12-16 17:02 ` Robert Marko
2025-12-16 18:52 ` Conor Dooley
2025-12-16 23:44 ` Michael Walle
2025-12-15 16:35 ` [PATCH v2 04/19] dt-bindings: arm: move AT91 to generic Microchip binding Robert Marko
2025-12-16 15:55 ` Krzysztof Kozlowski
2025-12-16 16:54 ` Robert Marko
2025-12-16 16:28 ` Alexandre Belloni
2025-12-16 16:56 ` Robert Marko
2025-12-16 17:26 ` Alexandre Belloni
2025-12-16 19:21 ` Conor Dooley
2025-12-16 19:35 ` Robert Marko
2025-12-16 22:40 ` Alexandre Belloni
2025-12-16 22:40 ` Alexandre Belloni
2025-12-17 12:33 ` Robert Marko
2025-12-15 16:35 ` [PATCH v2 05/19] dt-bindings: arm: microchip: move SparX-5 " Robert Marko
2025-12-16 15:58 ` Krzysztof Kozlowski
2025-12-16 17:01 ` Robert Marko
2025-12-16 18:50 ` Conor Dooley
2025-12-17 13:23 ` Krzysztof Kozlowski [this message]
2025-12-17 13:32 ` Robert Marko
2025-12-15 16:35 ` [PATCH v2 06/19] dt-bindings: mfd: atmel,sama5d2-flexcom: add microchip,lan9691-flexcom Robert Marko
2025-12-16 18:38 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 07/19] dt-bindings: serial: atmel,at91-usart: add microchip,lan9691-usart Robert Marko
2025-12-16 18:06 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 08/19] dt-bindings: spi: at91: add microchip,lan9691-spi Robert Marko
2025-12-16 18:05 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 09/19] dt-bindings: i2c: atmel,at91sam: add microchip,lan9691-i2c Robert Marko
2025-12-16 18:05 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 10/19] dt-bindings: rng: atmel,at91-trng: add microchip,lan9691-trng Robert Marko
2025-12-16 18:04 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 11/19] dt-bindings: crypto: atmel,at91sam9g46-aes: add microchip,lan9691-aes Robert Marko
2025-12-16 18:03 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 12/19] dt-bindings: crypto: atmel,at91sam9g46-sha: add microchip,lan9691-sha Robert Marko
2025-12-16 18:03 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 13/19] dt-bindings: dma: atmel: add microchip,lan9691-dma Robert Marko
2025-12-16 17:36 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 14/19] dt-bindings: net: mscc-miim: add microchip,lan9691-miim Robert Marko
2025-12-16 17:34 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 15/19] dt-bindings: hwmon: sparx5: add microchip,lan9691-temp Robert Marko
2025-12-16 17:34 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 16/19] dt-bindings: pinctrl: pinctrl-microchip-sgpio: add LAN969x Robert Marko
2025-12-16 17:33 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 17/19] arm64: dts: microchip: add LAN969x support Robert Marko
2025-12-15 16:35 ` [PATCH v2 18/19] dt-bindings: arm: microchip: document EV23X71A board Robert Marko
2025-12-16 17:32 ` Conor Dooley
2025-12-15 16:35 ` [PATCH v2 19/19] arm64: dts: microchip: add " Robert Marko
2025-12-16 13:11 ` [PATCH v2 01/19] include: dt-bindings: add LAN969x clock bindings Rob Herring
2025-12-16 15:56 ` Krzysztof Kozlowski
2025-12-16 15:57 ` Krzysztof Kozlowski
2025-12-16 16:59 ` Robert Marko
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=3d6f254c-d53f-47d9-8081-8506d202bf9d@kernel.org \
--to=krzk@kernel.org \
--cc=Ryan.Wanner@microchip.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=charan.pedumuru@microchip.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jirislaby@kernel.org \
--cc=kavyasree.kotagiri@microchip.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=lee@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luka.perkov@sartura.hr \
--cc=mturquette@baylibre.com \
--cc=mwalle@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=olivia@selenic.com \
--cc=pabeni@redhat.com \
--cc=radu_nicolae.pirea@upb.ro \
--cc=richard.genoud@bootlin.com \
--cc=richardcochran@gmail.com \
--cc=robert.marko@sartura.hr \
--cc=robh@kernel.org \
--cc=romain.sioen@microchip.com \
--cc=sboyd@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=vkoul@kernel.org \
--cc=wsa+renesas@sang-engineering.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 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).