From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com,
alexandre.torgue@foss.st.com, andrew+netdev@lunn.ch,
wens@csie.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, jernej.skrabec@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-sunxi@lists.linux.dev, mcoquelin.stm32@gmail.com,
netdev@vger.kernel.org, pabeni@redhat.com, samuel@sholland.org
Subject: Re: [PATCH net-next] net: stmmac: always allocate mac_device_info
Date: Thu, 13 Nov 2025 16:10:09 +0000 [thread overview]
Message-ID: <176305020974.908070.1045942084214006271.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <E1vImWK-0000000DrIx-28vO@rmk-PC.armlinux.org.uk>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 11 Nov 2025 11:26:44 +0000 you wrote:
> The ->setup() method implemented by dwmac-loongson and dwmac-sun8i
> allocate the mac_device_info structure, as does stmmac_hwif_init().
> This makes no sense.
>
> Have stmmac_hwif_init() always allocate this structure, and pass it to
> the ->setup() method to initialise when it is provided. Rename this
> method to "mac_setup" to more accurately describe what it is doing.
>
> [...]
Here is the summary with links:
- [net-next] net: stmmac: always allocate mac_device_info
https://git.kernel.org/netdev/net-next/c/f694d215d340
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-11-13 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 11:26 [PATCH net-next] net: stmmac: always allocate mac_device_info Russell King (Oracle)
2025-11-13 16: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=176305020974.908070.1045942084214006271.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=jernej.skrabec@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=samuel@sholland.org \
--cc=wens@csie.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 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.