From: Florian Fainelli <f.fainelli@gmail.com>
To: Matthew Hagan <mnhagan88@gmail.com>
Cc: "Christian Lamparter" <chunkeey@gmail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Rob Herring" <robh+dt@kernel.org>, "Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] net: bgmac-platform: handle mac-address deferral
Date: Sat, 25 Sep 2021 19:21:12 -0700 [thread overview]
Message-ID: <05f4baaf-24cc-da1a-a23d-7f033ba528f1@gmail.com> (raw)
In-Reply-To: <20210925113628.1044111-1-mnhagan88@gmail.com>
On 9/25/2021 4:36 AM, Matthew Hagan wrote:
> This patch is a replication of Christian Lamparter's "net: bgmac-bcma:
> handle deferred probe error due to mac-address" patch for the
> bgmac-platform driver [1].
>
> As is the case with the bgmac-bcma driver, this change is to cover the
> scenario where the MAC address cannot yet be discovered due to reliance
> on an nvmem provider which is yet to be instantiated, resulting in a
> random address being assigned that has to be manually overridden.
>
> [1] https://lore.kernel.org/netdev/20210919115725.29064-1-chunkeey@gmail.com
>
> Signed-off-by: Matthew Hagan <mnhagan88@gmail.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
prev parent reply other threads:[~2021-09-26 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 11:36 [PATCH 1/2] net: bgmac-platform: handle mac-address deferral Matthew Hagan
2021-09-25 11:36 ` [PATCH 2/2] ARM: dts: NSP: MX6X: get mac-address from eeprom Matthew Hagan
2021-09-25 16:48 ` [PATCH 1/2] net: bgmac-platform: handle mac-address deferral Andrew Lunn
2021-09-26 2:21 ` Florian Fainelli [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=05f4baaf-24cc-da1a-a23d-7f033ba528f1@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chunkeey@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mnhagan88@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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).