From: Florian Fainelli <florian.fainelli@broadcom.com>
To: bcm-kernel-feedback-list@broadcom.com,
Rosen Penev <rosenp@gmail.com>,
devicetree@vger.kernel.org
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"moderated list:BROADCOM BCM5301X ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 2/4] ARM: dts: BCM5301X: panamera: set WAN MAC from nvram
Date: Mon, 16 Mar 2026 13:44:06 -0700 [thread overview]
Message-ID: <20260316204406.2145139-1-florian.fainelli@broadcom.com> (raw)
In-Reply-To: <20260225230827.21715-3-rosenp@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
On Wed, 25 Feb 2026 15:08:25 -0800, Rosen Penev <rosenp@gmail.com> wrote:
> The MAC address from the stock firmare is offset by 1. Define it
> properly to avoid having to override it in userspace.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian
next prev parent reply other threads:[~2026-03-16 20:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 23:08 [PATCHv2 0/4] ARM: dts: BCM5301X: add WAN MAC assignments Rosen Penev
2026-02-25 23:08 ` [PATCHv2 1/4] ARM: dts: BCM5301X: EA9200: set WAN MAC from nvram Rosen Penev
2026-03-16 20:43 ` Florian Fainelli
2026-02-25 23:08 ` [PATCHv2 2/4] ARM: dts: BCM5301X: panamera: " Rosen Penev
2026-03-16 20:44 ` Florian Fainelli [this message]
2026-02-25 23:08 ` [PATCHv2 3/4] ARM: dts: BCM5301X: AC3100: " Rosen Penev
2026-03-16 20:44 ` Florian Fainelli
2026-02-25 23:08 ` [PATCHv2 4/4] ARM: dts: BCM5301X: AC5300: " Rosen Penev
2026-02-26 10:29 ` kernel test robot
2026-03-16 20:44 ` Florian Fainelli
2026-03-16 21:09 ` Rosen Penev
2026-03-16 21:11 ` Florian Fainelli
2026-03-16 21:13 ` Rosen Penev
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=20260316204406.2145139-1-florian.fainelli@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rosenp@gmail.com \
--cc=zajec5@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