From: patchwork-bot+netdevbpf@kernel•org
To: Andrew Halaney <ahalaney@redhat•com>
Cc: fancer.lancer@gmail•com, andrew@lunn•ch,
alexandre.torgue@foss•st.com, joabreu@synopsys•com,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, mcoquelin.stm32@gmail•com,
netdev@vger•kernel.org, linux-stm32@st-md-mailman•stormreply.com,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org, bartosz.golaszewski@linaro•org
Subject: Re: [PATCH net-next v4] net: stmmac: don't create a MDIO bus if unnecessary
Date: Fri, 15 Dec 2023 09:40:24 +0000 [thread overview]
Message-ID: <170263322448.1975.8565502940787597440.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231212-stmmac-no-mdio-node-v4-1-c121068ccd17@redhat.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft•net>:
On Tue, 12 Dec 2023 16:07:36 -0600 you wrote:
> Currently a MDIO bus is created if the devicetree description is either:
>
> 1. Not fixed-link
> 2. fixed-link but contains a MDIO bus as well
>
> The "1" case above isn't always accurate. If there's a phy-handle,
> it could be referencing a phy on another MDIO controller's bus[1]. In
> this case, where the MDIO bus is not described at all, currently
> stmmac will make a MDIO bus and scan its address space to discover
> phys (of which there are none). This process takes time scanning a bus
> that is known to be empty, delaying time to complete probe.
>
> [...]
Here is the summary with links:
- [net-next,v4] net: stmmac: don't create a MDIO bus if unnecessary
https://git.kernel.org/netdev/net-next/c/f3c2caacee82
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:[~2023-12-15 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 22:07 [PATCH net-next v4] net: stmmac: don't create a MDIO bus if unnecessary Andrew Halaney
2023-12-15 9:40 ` 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=170263322448.1975.8565502940787597440.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=ahalaney@redhat$(echo .)com \
--cc=alexandre.torgue@foss$(echo .)st.com \
--cc=andrew@lunn$(echo .)ch \
--cc=bartosz.golaszewski@linaro$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=fancer.lancer@gmail$(echo .)com \
--cc=joabreu@synopsys$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-stm32@st-md-mailman$(echo .)stormreply.com \
--cc=mcoquelin.stm32@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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