From: patchwork-bot+netdevbpf@kernel•org
To: Christophe Roullier <christophe.roullier@foss•st.com>
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, robh+dt@kernel•org,
krzysztof.kozlowski+dt@linaro•org, conor+dt@kernel•org,
mcoquelin.stm32@gmail•com, alexandre.torgue@foss•st.com,
richardcochran@gmail•com, joabreu@synopsys•com,
lgirdwood@gmail•com, broonie@kernel•org, marex@denx•de,
netdev@vger•kernel.org, devicetree@vger•kernel.org,
linux-stm32@st-md-mailman•stormreply.com,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org
Subject: Re: [net-next,PATCH v2 0/2] Fixes for stm32-dwmac driver fails to probe
Date: Tue, 02 Jul 2024 13:50:28 +0000 [thread overview]
Message-ID: <171992822898.3744.15499171958760914768.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240701064838.425521-1-christophe.roullier@foss.st.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat•com>:
On Mon, 1 Jul 2024 08:48:36 +0200 you wrote:
> Mark Brown found issue during stm32-dwmac probe:
>
> For the past few days networking has been broken on the Avenger 96, a
> stm32mp157a based platform. The stm32-dwmac driver fails to probe:
>
> <6>[ 1.894271] stm32-dwmac 5800a000.ethernet: IRQ eth_wake_irq not found
> <6>[ 1.899694] stm32-dwmac 5800a000.ethernet: IRQ eth_lpi not found
> <6>[ 1.905849] stm32-dwmac 5800a000.ethernet: IRQ sfty not found
> <3>[ 1.912304] stm32-dwmac 5800a000.ethernet: Unable to parse OF data
> <3>[ 1.918393] stm32-dwmac 5800a000.ethernet: probe with driver stm32-dwmac failed with error -75
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: stmmac: dwmac-stm32: Add test to verify if ETHCK is used before checking clk rate
https://git.kernel.org/netdev/net-next/c/3cd1d4651ceb
- [net-next,v2,2/2] net: stmmac: dwmac-stm32: update err status in case different of stm32mp13
https://git.kernel.org/netdev/net-next/c/f8dbe58e2f1a
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-07-02 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 6:48 [net-next,PATCH v2 0/2] Fixes for stm32-dwmac driver fails to probe Christophe Roullier
2024-07-01 6:48 ` [net-next,PATCH v2 1/2] net: stmmac: dwmac-stm32: Add test to verify if ETHCK is used before checking clk rate Christophe Roullier
2024-07-02 13:45 ` Paolo Abeni
2024-07-01 6:48 ` [net-next,PATCH v2 2/2] net: stmmac: dwmac-stm32: update err status in case different of stm32mp13 Christophe Roullier
2024-07-02 13:50 ` 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=171992822898.3744.15499171958760914768.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=alexandre.torgue@foss$(echo .)st.com \
--cc=broonie@kernel$(echo .)org \
--cc=christophe.roullier@foss$(echo .)st.com \
--cc=conor+dt@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=edumazet@google$(echo .)com \
--cc=joabreu@synopsys$(echo .)com \
--cc=krzysztof.kozlowski+dt@linaro$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=lgirdwood@gmail$(echo .)com \
--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=marex@denx$(echo .)de \
--cc=mcoquelin.stm32@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=richardcochran@gmail$(echo .)com \
--cc=robh+dt@kernel$(echo .)org \
/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