Re: [GIT PULL v3] arm/arm64: dts: socfpga: updates for v6.20, version 3

[Krzysztof Kozlowski <krzk@kernel.org>]

On 03/02/2026 04:32, Dinh Nguyen wrote:
> SoCFPGA DTS updates for v6.20, version 3
> - dt-bindings updates:
> 	- Add intel,socfpga-agilex5-socdk-modular for the Agilex5 mod board
> 	- Add intel,socfpga-agilex-emmc for the Agilex eMMC daughter board
> 	- Move entries in intel,socfpga.yaml into altera.yaml
> 	- Add syscon as a fallback for sys-mgr
> 
> - Add dma-cohrerent property for Agilex5 NAND and DMA
> - Add support for the Agilex5 modular board
> - Add IOMMUS property for ethernet nodes for Agilex5
> - Use lowercase hex for dts files
> - Add #address-cells and #size-cells for sram
> - Fix dtbs_check warning for fpga-region
> - Move dma controller node for Agilex5 under simple-bus
> - Add support for the Agilex eMMC daughter board
> 
> ----------------------------------------------------------------
> Dinh Nguyen (4):
>       dt-bindings: arm: altera: combine Intel's SoCFPGA into altera.yaml
>       dt-bindings: altera: document syscon as fallback for sys-mgr
>       ARM: dts: socfpga: add #address-cells and #size-cells for sram node
>       ARM: dts: socfpga: fix dtbs_check warning for fpga-region
> 
> Khairul Anuar Romli (2):
>       arm64: dts: socfpga: agilex5: Add dma-coherent property
>       arm64: dts: intel: agilex5: Add simple-bus node on top of dma controller node
> 
> Krzysztof Kozlowski (1):
>       arm64: dts: altera: Use lowercase hex
> 
> Nazim Amirul (1):
>       arm64: dts: socfpga: agilex5: Add IOMMUS property for ethernet nodes
> 
> Ng Tze Yee (2):
>       arm64: dts: socfpga: agilex: add emmc support
>       dt-bindings: intel: Add Agilex eMMC support
> 
> Niravkumar L Rabara (2):
>       dt-bindings: intel: Add Agilex5 SoCFPGA modular board
>       arm64: dts: socfpga: agilex5: add support for modular board
> 

I checked few of here and none of them were in the next at the time you
sent pull request, even though some were sent and applied long time ago.

Like this one - applied on 24th Dec:
https://lore.kernel.org/all/4bd0643c-b9d4-49fa-92a5-f8878f75d1e1@kernel.org/

but never in the next.

In case if something is not clear: there must be in the linux-next at
shortest interval after you apply the patches, so the NEXT linux-next
after you apply.

I already commented about this on 28 Jan and then again on 5 Feb. I
don't understand why I need to ask three times about this, but that's
the last time I ask/remind.

Best regards,
Krzysztof