From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>,
jonas.gorski@gmail.com, andrew@lunn.ch, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, dgcbueu@gmail.com
Subject: Re: [PATCH net-next v2 3/3] net: dsa: b53: support legacy FCS tags
Date: Tue, 10 Jun 2025 09:40:36 -0700 [thread overview]
Message-ID: <a94c50ea-1658-48e3-8f6c-f0b6657b1d79@broadcom.com> (raw)
In-Reply-To: <20250610163154.281454-4-noltari@gmail.com>
On 6/10/25 09:31, Álvaro Fernández Rojas wrote:
> Commit 46c5176c586c ("net: dsa: b53: support legacy tags") introduced
> support for legacy tags, but it turns out that BCM5325 and BCM5365
> switches require the original FCS value and length, so they have to be
> treated differently.
>
> Fixes: 46c5176c586c ("net: dsa: b53: support legacy tags")
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
prev parent reply other threads:[~2025-06-10 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 16:31 [PATCH net-next v2 0/3] net: dsa: brcm: add legacy FCS tag Álvaro Fernández Rojas
2025-06-10 16:31 ` [PATCH net-next v2 1/3] net: dsa: tag_brcm: legacy: reorganize functions Álvaro Fernández Rojas
2025-06-10 16:38 ` Florian Fainelli
2025-06-10 16:31 ` [PATCH net-next v2 2/3] net: dsa: tag_brcm: add support for legacy FCS tags Álvaro Fernández Rojas
2025-06-11 21:46 ` Jakub Kicinski
2025-06-10 16:31 ` [PATCH net-next v2 3/3] net: dsa: b53: support " Álvaro Fernández Rojas
2025-06-10 16:40 ` 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=a94c50ea-1658-48e3-8f6c-f0b6657b1d79@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dgcbueu@gmail.com \
--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=noltari@gmail.com \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®