[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <trinity-eafa403a-1d9f-4842-a65c-84badd4fa6ee-1750005734980@trinity-msg-rest-gmx-gmx-live-847b5f5c86-84n87>
Date: Sun, 15 Jun 2025 16:42:15 +0000
From: Frank Wunderlich <frank-w@...lic-files.de>
To: linux@...web.de, nbd@....name, sean.wang@...iatek.com,
lorenzo@...nel.org, andrew+netdev@...n.ch, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org,
horms@...nel.org, daniel@...rotopia.org
Subject: Aw: [net-next v3 0/3] rework IRQ handling in mtk_eth_soc
> Gesendet: Sonntag, 15. Juni 2025 um 17:03
> Von: "Frank Wunderlich" <linux@...web.de>
sorry, missed the changelog:
v3:
added patches
- #2 (add constants for irq index)
- #3 (skip first IRQ on ! MTK_SHARED_INT)
to the v2 non-series patch
https://patchwork.kernel.org/project/netdevbpf/patch/20250615084521.32329-1-linux@fw-web.de/
Tested on BPI-R4/mt7988 with IRQ names and BPI-R2/mt7623 and BPI-R3/mt7986 with upstreamed
dts via index-mode.
I do not have any MTK_SHARED_INT (mt7621/mt7628) boards to testing.
Powered by blists - more mailing lists