From: patchwork-bot+netdevbpf@kernel.org
To: Saravana Kannan <saravanak@google.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, kuba@kernel.org, jon.mason@broadcom.com,
david.daney@cavium.com, maz@kernel.org, narmstrong@baylibre.com,
khilman@baylibre.com, kernel-team@android.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/3] Clean up and fix error handling in mdio_mux_init()
Date: Wed, 18 Aug 2021 09:50:06 +0000 [thread overview]
Message-ID: <162928020609.23266.3797943730217405111.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210818033804.3281057-1-saravanak@google.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Tue, 17 Aug 2021 20:38:00 -0700 you wrote:
> This patch series was started due to -EPROBE_DEFER not being handled
> correctly in mdio_mux_init() and causing issues [1]. While at it, I also
> did some more error handling fixes and clean ups. The -EPROBE_DEFER fix is
> the last patch.
>
> Ideally, in the last patch we'd treat any error similar to -EPROBE_DEFER
> but I'm not sure if it'll break any board/platforms where some child
> mdiobus never successfully registers. If we treated all errors similar to
> -EPROBE_DEFER, then none of the child mdiobus will work and that might be a
> regression. If people are sure this is not a real case, then I can fix up
> the last patch to always fail the entire mdio-mux init if any of the child
> mdiobus registration fails.
>
> [...]
Here is the summary with links:
- [net,v3,1/3] net: mdio-mux: Delete unnecessary devm_kfree
https://git.kernel.org/netdev/net/c/663d946af5fb
- [net,v3,2/3] net: mdio-mux: Don't ignore memory allocation errors
https://git.kernel.org/netdev/net/c/99d81e942474
- [net,v3,3/3] net: mdio-mux: Handle -EPROBE_DEFER correctly
https://git.kernel.org/netdev/net/c/7bd0cef5dac6
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-08-18 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 3:38 [PATCH net v3 0/3] Clean up and fix error handling in mdio_mux_init() Saravana Kannan
2021-08-18 3:38 ` [PATCH net v3 1/3] net: mdio-mux: Delete unnecessary devm_kfree Saravana Kannan
2021-08-18 3:38 ` [PATCH net v3 2/3] net: mdio-mux: Don't ignore memory allocation errors Saravana Kannan
2021-08-18 3:38 ` [PATCH net v3 3/3] net: mdio-mux: Handle -EPROBE_DEFER correctly Saravana Kannan
2021-08-18 9: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=162928020609.23266.3797943730217405111.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=hkallweit1@gmail.com \
--cc=jon.mason@broadcom.com \
--cc=kernel-team@android.com \
--cc=khilman@baylibre.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maz@kernel.org \
--cc=narmstrong@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=saravanak@google.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).