Re: [PATCH net-next 11/13] net/mlx5: LAG, drop stale esw_shared_ingress_acl gate from shared FDB

[sashiko-bot@kernel.org]

> From: Shay Drory <shayd@nvidia.com>
> 
> The shared-FDB support check still requires the esw_shared_ingress_acl
> capability. That capability backed the merged uplink ingress ACL, where
> the slave uplink's ingress-ACL root was pointed at the master's
> (esw_set_uplink_slave_ingress_root()). That handling was removed in
> commit 82e86a6c7109 ("net/mlx5: E-switch, remove special uplink ingress
> ACL handling") once both uplinks were tagged with the same reserved
> metadata (MLX5_ESW_METADATA_RSVD_UPLINK) - a single FDB rule then
> matches traffic from either uplink, with no shared ingress ACL involved.
> 
> The capability check was left behind and has been dead since: the driver
> programs no shared ingress ACL, yet the check still keeps otherwise
> shared-FDB-capable devices out of shared FDB. Drop it.
> 
> Signed-off-by: Shay Drory <shayd@nvidia.com>
> Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
> Reviewed-by: Akiva Goldberger <agoldberger@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260923103830.1183-1-tariqt@nvidia.com?part=11