From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Semih Baskan <strst.gs@gmail.com>, Jonas Gorski <jonas.gorski@gmail.com>
Cc: andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
vladimir.oltean@nxp.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] net: dsa: b53: fix 8021q uppers on standalone ports
Date: Mon, 31 Aug 2026 17:24:46 -0700 [thread overview]
Message-ID: <739079cd-dc83-4b53-a3a9-a7e610379d19@broadcom.com> (raw)
In-Reply-To: <CAAsRjRktqEx+-CLDO_q6rLUBe1dtRQPH1NkX4xy7ichx79yGPQ@mail.gmail.com>
On 8/31/2026 3:17 AM, Semih Baskan wrote:
> Hi Jonas,
>
> On Mon, Aug 31, 2026 at 12:34 PM Jonas Gorski <jonas.gorski@gmail.com> wrote:
>> I really think we should just fix up the in-tree device trees and then
>> complain loudly about the broken configuration on probe in case there
>> are out of tree device trees with the broken configuration.
>
> I agree, fixing this up in the device tree is the more robust way.
> In the meantime OpenWrt can carry these patches as a band aid for
> the affected boards.
But you control exact how the DTS gets distributed in OpenWrt, why not
just fix all of the DTSes there and have the users confirm that using
port 8 as the IMP works?
Don't get me wrong, I am very appreciative that you spent a decent
amount of time trying to come up with some sort of solution.
Thanks
--
Florian
next prev parent reply other threads:[~2026-09-01 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 8:52 [PATCH net v3 0/2] net: dsa: b53: fix 8021q uppers on standalone ports Semih Baskan
2026-08-31 8:52 ` [PATCH net v3 1/2] net: dsa: let drivers offload " Semih Baskan
2026-08-31 10:20 ` Vladimir Oltean
2026-08-31 8:52 ` [PATCH net v3 2/2] net: dsa: b53: " Semih Baskan
2026-08-31 9:34 ` [PATCH net v3 0/2] net: dsa: b53: fix " Jonas Gorski
2026-08-31 10:17 ` Semih Baskan
2026-09-01 0:24 ` Florian Fainelli [this message]
2026-09-01 5:29 ` Semih Baskan
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=739079cd-dc83-4b53-a3a9-a7e610379d19@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=strst.gs@gmail.com \
--cc=vladimir.oltean@nxp.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