From: patchwork-bot+netdevbpf@kernel.org
To: Robert Hancock <robert.hancock@calian.com>
Cc: radhey.shyam.pandey@xilinx.com, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net] net: axienet: Handle deferred probe on clock properly
Date: Sat, 13 Feb 2021 01:45:49 +0000 [thread overview]
Message-ID: <161318074961.24767.15053675195382667062.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210213001748.2556885-1-robert.hancock@calian.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 12 Feb 2021 18:17:48 -0600 you wrote:
> This driver is set up to use a clock mapping in the device tree if it is
> present, but still work without one for backward compatibility. However,
> if getting the clock returns -EPROBE_DEFER, then we need to abort and
> return that error from our driver initialization so that the probe can
> be retried later after the clock is set up.
>
> Move clock initialization to earlier in the process so we do not waste as
> much effort if the clock is not yet available. Switch to use
> devm_clk_get_optional and abort initialization on any error reported.
> Also enable the clock regardless of whether the controller is using an MDIO
> bus, as the clock is required in any case.
>
> [...]
Here is the summary with links:
- [net] net: axienet: Handle deferred probe on clock properly
https://git.kernel.org/netdev/net/c/57baf8cc70ea
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:[~2021-02-13 1:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 0:17 [PATCH net] net: axienet: Handle deferred probe on clock properly Robert Hancock
2021-02-13 1:45 ` 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=161318074961.24767.15053675195382667062.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=radhey.shyam.pandey@xilinx.com \
--cc=robert.hancock@calian.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).