From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com,
alexandre.torgue@foss.st.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
pabeni@redhat.com, maxime.chevallier@bootlin.com
Subject: Re: [PATCH net-next v3 0/5] net: stmmac: socfpga: fix init ordering and cleanups
Date: Tue, 22 Apr 2025 09:10:53 +0000 [thread overview]
Message-ID: <174531305373.1477965.16027981733032970963.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <aAE2tKlImhwKySq_@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 17 Apr 2025 18:13:24 +0100 you wrote:
> Hi,
>
> This series fixes the init ordering of the socfpga probe function.
> The standard rule is to do all setup before publishing any device,
> and socfpga violates that. I can see no reason for this, but these
> patches have not been tested on hardware.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/5] net: stmmac: socfpga: init dwmac->stmmac_rst before registration
https://git.kernel.org/netdev/net-next/c/9276bfc2df92
- [net-next,v3,2/5] net: stmmac: socfpga: provide init function
https://git.kernel.org/netdev/net-next/c/0dbd4a6f57c2
- [net-next,v3,3/5] net: stmmac: socfpga: convert to stmmac_pltfr_pm_ops
https://git.kernel.org/netdev/net-next/c/6bf70d999aa9
- [net-next,v3,4/5] net: stmmac: socfpga: call set_phy_mode() before registration
https://git.kernel.org/netdev/net-next/c/91255347bba9
- [net-next,v3,5/5] net: stmmac: socfpga: convert to devm_stmmac_pltfr_probe()
https://git.kernel.org/netdev/net-next/c/1dbefd578d8b
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-04-22 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 17:13 [PATCH net-next v3 0/5] net: stmmac: socfpga: fix init ordering and cleanups Russell King (Oracle)
2025-04-17 17:13 ` [PATCH net-next v3 1/5] net: stmmac: socfpga: init dwmac->stmmac_rst before registration Russell King (Oracle)
2025-04-17 17:13 ` [PATCH net-next v3 2/5] net: stmmac: socfpga: provide init function Russell King (Oracle)
2025-04-17 17:13 ` [PATCH net-next v3 3/5] net: stmmac: socfpga: convert to stmmac_pltfr_pm_ops Russell King (Oracle)
2025-04-17 17:13 ` [PATCH net-next v3 4/5] net: stmmac: socfpga: call set_phy_mode() before registration Russell King (Oracle)
2025-04-17 17:13 ` [PATCH net-next v3 5/5] net: stmmac: socfpga: convert to devm_stmmac_pltfr_probe() Russell King (Oracle)
2025-04-18 9:25 ` [PATCH net-next v3 0/5] net: stmmac: socfpga: fix init ordering and cleanups Maxime Chevallier
2025-04-22 9: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=174531305373.1477965.16027981733032970963.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.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=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).