From: Mieczyslaw Nalewaj <namiltd@yahoo.com>
To: "Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Vladimir Oltean" <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Linus Walleij" <linusw@kernel.org>,
"Alvin Šipraga" <alsi@bang-olufsen.dk>,
"Yury Norov" <yury.norov@gmail.com>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Russell King" <linux@armlinux.org.uk>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Abdulkader Alrezej <abdulkader.alrezej@gmail.com>,
Yury Norov <ynorov@nvidia.com>
Subject: Re: [net-next PATCH v9 0/8] net: dsa: realtek: rtl8365mb: bridge offloading and VLAN support
Date: Sat, 30 May 2026 10:36:11 +0200 [thread overview]
Message-ID: <0c20ceb5-1cf7-4f83-9623-b5f5018f44af@yahoo.com> (raw)
In-Reply-To: <20260529-realtek_forward-v9-0-e7c61872d923@gmail.com>
On 5/29/2026 6:29 AM, Luiz Angelo Daros de Luca wrote:
> This series introduces bridge offloading, FDB management, and VLAN support
> for the Realtek rtl8365mb DSA switch driver. The primary goal is to
> enable hardware frame forwarding between bridge ports, reducing CPU
> overhead and providing advanced features like VLAN and FDB isolation.
>
> Some of these patches are based on original work by Alvin Šipraga,
> subsequently adapted and updated for the current net-next state.
>
> ---
> I attempted to reach Alvin for review of the final version but was
> unable to establish contact. Any regressions in this version are my
> responsibility.
>
> Changes in v9:
> * Patch 2 (DSA helpers):
> - Switch to dsa_switch_for_each_port() in the irq_setup error path.
> * Patch 4 (Table lookup):
> - Convert kdoc to standard comments.
> - Fix doc description for L2 write operation return value and
> data/addr on errors.
> - Removed misleading comment on RTL8365MB_TABLE_CTRL_PORT_MASK.
> * Patch 5 (VLAN support):
> - Do PVID first in port_vlan_add() to avoid reverting vlan4k changes
> if it fails.
> - Do not use dsa_switch_for_each_port_continue_reverse() after the
> loop ends (use-after-iterator).
> - Simplify PVID helpers to receive VID instead of switchdev vlan.
> - Avoid redundant writes in the PVID error path.
> - Convert kdoc to standard comments.
> * Patch 6 (Bridge Join/Leave):
> - Do not use dsa_switch_for_each_port_continue_reverse() after the
> loop ends (use-after-iterator).
> - Link to v8: https://patch.msgid.link/20260525-realtek_forward-v8-0-5eb80a4675be@gmail.com
Sashiko found no issues in the v9 code: https://sashiko.dev/#/patchset/20260529-realtek_forward-v9-0-e7c61872d923%40gmail.com
next prev parent reply other threads:[~2026-05-30 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 4:29 Luiz Angelo Daros de Luca
2026-05-29 4:29 ` [net-next PATCH v9 1/8] net: dsa: realtek: rtl8365mb: use ERR_PTR Luiz Angelo Daros de Luca
2026-05-29 4:29 ` [net-next PATCH v9 2/8] net: dsa: realtek: rtl8365mb: use dsa helpers for port iteration Luiz Angelo Daros de Luca
2026-05-29 4:29 ` [net-next PATCH v9 3/8] net: dsa: realtek: rtl8365mb: prepare for multiple source files Luiz Angelo Daros de Luca
2026-05-29 4:29 ` [net-next PATCH v9 4/8] net: dsa: realtek: rtl8365mb: add table lookup interface Luiz Angelo Daros de Luca
2026-05-29 4:29 ` [net-next PATCH v9 5/8] net: dsa: realtek: rtl8365mb: add VLAN support Luiz Angelo Daros de Luca
2026-05-29 4:29 ` [net-next PATCH v9 6/8] net: dsa: realtek: rtl8365mb: add port_bridge_{join,leave} Luiz Angelo Daros de Luca
2026-05-29 4:29 ` [net-next PATCH v9 7/8] net: dsa: realtek: rtl8365mb: add FDB support Luiz Angelo Daros de Luca
2026-05-29 4:29 ` [net-next PATCH v9 8/8] net: dsa: realtek: rtl8365mb: add bridge port flags Luiz Angelo Daros de Luca
2026-05-30 8:36 ` Mieczyslaw Nalewaj [this message]
2026-05-30 11:00 ` [net-next PATCH v9 0/8] net: dsa: realtek: rtl8365mb: bridge offloading and VLAN support Luiz Angelo Daros de Luca
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=0c20ceb5-1cf7-4f83-9623-b5f5018f44af@yahoo.com \
--to=namiltd@yahoo.com \
--cc=abdulkader.alrezej@gmail.com \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=ynorov@nvidia.com \
--cc=yury.norov@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
all inboxes | Powered by JetHome®