Re: [PATCH v7 0/9] DTS updates for system1 BMC

From
Andrew Jeffery <andrew@codeconstruct.com.au>
Date
2025-02-05 00:05:50
Also in
linux-arm-kernel, linux-aspeed, linux-devicetree, lkml
Reply to
Ninad Palsule, 2025-02-04
On Tue, 2025-02-04 at 13:40 -0600, Ninad Palsule wrote:
quoted
This one needs an ack from Linus W or Bartosz if I'm to take it.
However, it's also causing some grief from Rob's bot:

https://lore.kernel.org/all/173859694889.2601726.10618336219726193824.robh@kernel.org/ (local)

As the reported nodes should all be hogs the name shouldn't matter
anywhere else (as far as I'm aware). It would be nice if all the
warnings were cleaned up before we merged the binding update. That way
we don't cause everyone else looking at the CHECK_DTBS=y output more
grief than they already get for the Aspeed devicetrees.

In order to not get bogged down it might be worth splitting out both
the IPMB- and GPIO- related patches like you did the FTGMAC100 patch,
and then I can merge what remains (from a quick look they seem
relatively uncontroversial).
The warnings are fixed by different patch by Krzysztof. As there are no 
more changes then I will wait for other responses. If I don't get those 
response in couple of days then I will split it.
https://lore.kernel.org/linux-kernel/20250116085947.87241-1-krzysztof.kozlowski@linaro.org/ (local)
That patch fixes a couple of Marvell systems. I think you might have
meant this:

https://lore.kernel.org/all/20250116090009.87338-1-krzysztof.kozlowski@linaro.org/ (local)

In which case, I've applied it.

Thanks,

Andrew
Thread (18 messages) 18 messages, 5 authors, last reply 2025-02-13
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help