From: patchwork-bot+netdevbpf@kernel.org
To: Mauri Sandberg <maukka@ext.kapsi.fi>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
sebastian.hesselbarth@gmail.com, davem@davemloft.net,
kuba@kernel.org, andrew@lunn.ch
Subject: Re: [PATCH v2] net: mv643xx_eth: process retval from of_get_mac_address
Date: Thu, 24 Feb 2022 18:20:10 +0000 [thread overview]
Message-ID: <164572681056.6045.9971807699908202532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220223142337.41757-1-maukka@ext.kapsi.fi>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 23 Feb 2022 16:23:37 +0200 you wrote:
> Obtaining a MAC address may be deferred in cases when the MAC is stored
> in an NVMEM block, for example, and it may not be ready upon the first
> retrieval attempt and return EPROBE_DEFER.
>
> It is also possible that a port that does not rely on NVMEM has been
> already created when getting the defer request. Thus, also the resources
> allocated previously must be freed when doing a roll-back.
>
> [...]
Here is the summary with links:
- [v2] net: mv643xx_eth: process retval from of_get_mac_address
https://git.kernel.org/netdev/net/c/42404d8f1c01
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:[~2022-02-24 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 6:24 [PATCH] net: mv643xx_eth: handle EPROBE_DEFER Mauri Sandberg
2022-02-21 12:21 ` Andrew Lunn
2022-02-21 18:25 ` Mauri Sandberg
2022-02-21 22:15 ` Andrew Lunn
2022-02-22 5:42 ` Mauri Sandberg
2022-02-23 14:23 ` [PATCH v2] net: mv643xx_eth: process retval from of_get_mac_address Mauri Sandberg
2022-02-24 16:57 ` Jakub Kicinski
2022-02-24 17:43 ` Andrew Lunn
2022-02-24 18:20 ` 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=164572681056.6045.9971807699908202532.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maukka@ext.kapsi.fi \
--cc=netdev@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.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