From: Florian Fainelli <florian.fainelli@broadcom.com>
To: bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <zajec5@gmail.com>
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH 2/3] ARM: dts: BCM53573: Describe BCM53125 switch ports in the main DTS
Date: Fri, 28 Jul 2023 10:22:14 -0700 [thread overview]
Message-ID: <20230728172214.723281-1-florian.fainelli@broadcom.com> (raw)
In-Reply-To: <20230723195416.7831-2-zajec5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 557 bytes --]
From: Florian Fainelli <f.fainelli@gmail.com>
On Sun, 23 Jul 2023 21:54:15 +0200, Rafał Miłecki <zajec5@gmail.com> wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> BCM53125 always has 5 ports with GPHYs (for LAN/WAN ports) and 2 IMP
> ports. It seems the best place to describe that in the main .dtsi.
> Device specific bits can go to device .dts files. This will help
> avoiding some code duplication.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/master, thanks!
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
next prev parent reply other threads:[~2023-07-28 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 19:54 [PATCH 1/3] ARM: dts: BCM53573: Fix Tenda AC9 switch CPU port Rafał Miłecki
2023-07-23 19:54 ` [PATCH 2/3] ARM: dts: BCM53573: Describe BCM53125 switch ports in the main DTS Rafał Miłecki
2023-07-28 17:22 ` Florian Fainelli [this message]
2023-07-23 19:54 ` [PATCH 3/3] ARM: dts: BCM53573: Add BCM53125 switch port 5 Rafał Miłecki
2023-07-28 17:23 ` Florian Fainelli
2023-07-28 17:21 ` [PATCH 1/3] ARM: dts: BCM53573: Fix Tenda AC9 switch CPU port Florian Fainelli
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=20230728172214.723281-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=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).