From: patchwork-bot+netdevbpf@kernel.org
To: Heiko Stuebner <heiko@sntech.de>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
jonas@kwiboo.se
Subject: Re: [PATCH v2 0/5] DWMAC support for Rockchip RK3506
Date: Sat, 25 Oct 2025 02:10:41 +0000 [thread overview]
Message-ID: <176135824149.4124588.13375979090680382599.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251023111213.298860-1-heiko@sntech.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 23 Oct 2025 13:12:07 +0200 you wrote:
> Some cleanups to the DT binding for Rockchip variants of the dwmac
> and adding the RK3506 support on top.
>
> As well as the driver-glue needed for setting up the correct RMII
> speed seitings.
>
> changes in v2:
> - add Conor's Acks to dt-bindings
> - add Andrew's Reviews to first 3 patches
> I didn't add the driver Review, as I did address Jonas' comments
> - adapt to Jonas' comments in the driver
> - add a patch for a MAINTAINERS entry (Jakub)
>
> [...]
Here is the summary with links:
- [v2,1/5] dt-bindings: net: snps,dwmac: move rk3399 line to its correct position
https://git.kernel.org/netdev/net-next/c/32dd679b88d5
- [v2,2/5] dt-bindings: net: snps,dwmac: Sync list of Rockchip compatibles
https://git.kernel.org/netdev/net-next/c/e774c91dca45
- [v2,3/5] dt-bindings: net: rockchip-dwmac: Add compatible string for RK3506
https://git.kernel.org/netdev/net-next/c/4a667bec74b3
- [v2,4/5] ethernet: stmmac: dwmac-rk: Add RK3506 GMAC support
https://git.kernel.org/netdev/net-next/c/2010163a8ea4
- [v2,5/5] MAINTAINERS: add dwmac-rk glue driver to the main Rockchip entry
https://git.kernel.org/netdev/net-next/c/384d84263295
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-10-25 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 11:12 [PATCH v2 0/5] DWMAC support for Rockchip RK3506 Heiko Stuebner
2025-10-23 11:12 ` [PATCH v2 1/5] dt-bindings: net: snps,dwmac: move rk3399 line to its correct position Heiko Stuebner
2025-10-23 11:12 ` [PATCH v2 2/5] dt-bindings: net: snps,dwmac: Sync list of Rockchip compatibles Heiko Stuebner
2025-10-23 11:12 ` [PATCH v2 3/5] dt-bindings: net: rockchip-dwmac: Add compatible string for RK3506 Heiko Stuebner
2025-10-23 11:12 ` [PATCH v2 4/5] ethernet: stmmac: dwmac-rk: Add RK3506 GMAC support Heiko Stuebner
2025-10-23 11:12 ` [PATCH v2 5/5] MAINTAINERS: add dwmac-rk glue driver to the main Rockchip entry Heiko Stuebner
2025-10-23 18:57 ` Andrew Lunn
2025-10-23 20:48 ` Heiko Stuebner
2025-10-25 2:10 ` patchwork-bot+netdevbpf [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=176135824149.4124588.13375979090680382599.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).