From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: fancer.lancer@gmail.com, alexandre.torgue@foss.st.com,
ahalaney@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, joabreu@synopsys.com,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
pabeni@redhat.com, romain.gantois@bootlin.com
Subject: Re: [PATCH net-next v2 0/5] net: stmmac: provide platform select_pcs method
Date: Sat, 15 Jun 2024 02:10:34 +0000 [thread overview]
Message-ID: <171841743440.11975.7851912921042282735.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZmrLbdwv6ALoy+gs@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 13 Jun 2024 11:35:25 +0100 you wrote:
> Hi,
>
> This series adds a select_pcs() method to the stmmac platform data to
> allow platforms that need to provide their own PCSes to do so, moving
> the decision making into platform code.
>
> This avoids questions such as "what should the priority of XPCS vs
> some other platform PCS be?" and when we provide a PCS for the
> internal PCS, how that interacts with both the XPCS and platform
> provided PCS.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] net: stmmac: add select_pcs() platform method
https://git.kernel.org/netdev/net-next/c/6c3282a6b296
- [net-next,v2,2/5] net: stmmac: dwmac-intel: provide a select_pcs() implementation
https://git.kernel.org/netdev/net-next/c/135553da844c
- [net-next,v2,3/5] net: stmmac: dwmac-rzn1: provide select_pcs() implementation
https://git.kernel.org/netdev/net-next/c/804c9866e078
- [net-next,v2,4/5] net: stmmac: dwmac-socfpga: provide select_pcs() implementation
https://git.kernel.org/netdev/net-next/c/98a6d9f192d3
- [net-next,v2,5/5] net: stmmac: clean up stmmac_mac_select_pcs()
https://git.kernel.org/netdev/net-next/c/93f84152e4ae
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:[~2024-06-15 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 10:35 [PATCH net-next v2 0/5] net: stmmac: provide platform select_pcs method Russell King (Oracle)
2024-06-13 10:36 ` [PATCH net-next v2 1/5] net: stmmac: add select_pcs() platform method Russell King (Oracle)
2024-06-14 16:38 ` Serge Semin
2024-06-14 17:21 ` Russell King (Oracle)
2024-06-13 10:36 ` [PATCH net-next v2 2/5] net: stmmac: dwmac-intel: provide a select_pcs() implementation Russell King (Oracle)
2024-06-13 10:36 ` [PATCH net-next v2 3/5] net: stmmac: dwmac-rzn1: provide " Russell King (Oracle)
2024-06-13 10:36 ` [PATCH net-next v2 4/5] net: stmmac: dwmac-socfpga: " Russell King (Oracle)
2024-06-13 10:36 ` [PATCH net-next v2 5/5] net: stmmac: clean up stmmac_mac_select_pcs() Russell King (Oracle)
2024-06-15 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=171841743440.11975.7851912921042282735.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ahalaney@redhat.com \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fancer.lancer@gmail.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=romain.gantois@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.