From: patchwork-bot+netdevbpf@kernel•org
To: Michael Walle <michael@walle•cc>
Cc: horatiu.vultur@microchip•com, davem@davemloft•net,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
UNGLinuxDriver@microchip•com
Subject: Re: [PATCH net] net: lan966x: check devm_of_phy_get() for -EDEFER_PROBE
Date: Fri, 27 May 2022 04:48:33 +0000 [thread overview]
Message-ID: <165362691349.5864.17166538440351301920.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220525231239.1307298-1-michael@walle.cc>
Hello:
This patch was applied to bpf/bpf.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Thu, 26 May 2022 01:12:39 +0200 you wrote:
> At the moment, if devm_of_phy_get() returns an error the serdes
> simply isn't set. While it is bad to ignore an error in general, there
> is a particular bug that network isn't working if the serdes driver is
> compiled as a module. In that case, devm_of_phy_get() returns
> -EDEFER_PROBE and the error is silently ignored.
>
> The serdes is optional, it is not there if the port is using RGMII, in
> which case devm_of_phy_get() returns -ENODEV. Rearrange the error
> handling so that -ENODEV will be handled but other error codes will
> abort the probing.
>
> [...]
Here is the summary with links:
- [net] net: lan966x: check devm_of_phy_get() for -EDEFER_PROBE
https://git.kernel.org/bpf/bpf/c/b58cdd4388b1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-05-27 4:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 23:12 [PATCH net] net: lan966x: check devm_of_phy_get() for -EDEFER_PROBE Michael Walle
2022-05-27 4:48 ` patchwork-bot+netdevbpf [this message]
2022-05-27 7:54 ` Michael Walle
2022-05-27 22:52 ` Jakub Kicinski
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=165362691349.5864.17166538440351301920.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=UNGLinuxDriver@microchip$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=horatiu.vultur@microchip$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=michael@walle$(echo .)cc \
--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