From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, netdev@vger.kernel.org,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCHv3 0/2] RK3588 Ethernet Support
Date: Thu, 01 Sep 2022 10:10:16 +0000 [thread overview]
Message-ID: <166202701658.6021.5345078422266376617.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220830154559.61506-1-sebastian.reichel@collabora.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 30 Aug 2022 17:45:57 +0200 you wrote:
> This adds ethernet support for the RK3588(s) SoCs.
>
> Changes since PATCHv2:
> * Rebased to v6.0-rc1
> * Wrap DT bindings additions at 80 characters
> * Add Acked-by from Krzysztof
>
> [...]
Here is the summary with links:
- [PATCHv3,1/2] net: ethernet: stmmac: dwmac-rk: Add gmac support for rk3588
https://git.kernel.org/netdev/net-next/c/2f2b60a0ec28
- [PATCHv3,2/2] dt-bindings: net: rockchip-dwmac: add rk3588 gmac compatible
https://git.kernel.org/netdev/net-next/c/a2b77831427c
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:[~2022-09-01 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 15:45 [PATCHv3 0/2] RK3588 Ethernet Support Sebastian Reichel
2022-08-30 15:45 ` [PATCHv3 1/2] net: ethernet: stmmac: dwmac-rk: Add gmac support for rk3588 Sebastian Reichel
2022-08-30 15:45 ` [PATCHv3 2/2] dt-bindings: net: rockchip-dwmac: add rk3588 gmac compatible Sebastian Reichel
2022-09-01 10: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=166202701658.6021.5345078422266376617.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.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).