From: sashiko-bot@kernel.org
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org,
wsa+renesas@sang-engineering.com, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v2 10/12] net: dsa: rzn1-a5psw: Add fixed frame length workaround for management port
Date: Sat, 03 Oct 2026 01:33:11 +0000 [thread overview]
Message-ID: <20261003013311.C246A1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20261001154326.754314-11-prabhakar.mahadev-lad.rj@bp.renesas.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] build: -Wdiscarded-qualifiers on of_data assignment
--
commit c1982503d53e92d2bb0e481c0cef9b75fe397c5c
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
net: dsa: rzn1-a5psw: Add fixed frame length workaround for management port
This commit adds a workaround for an ETHSW IP issue in SoCs like RZ/T2H where
the internal mgmt_tag_vld signal is asserted as a level instead of a pulse.
It provides a way to set a fixed maximum frame length on the management port
to prevent valid frames from being dropped.
> diff --git a/drivers/net/dsa/rzn1_a5psw.c b/drivers/net/dsa/rzn1_a5psw.c
> index 0b0b4055e6155..ce931442d49fd 100644
> --- a/drivers/net/dsa/rzn1_a5psw.c
> +++ b/drivers/net/dsa/rzn1_a5psw.c
> @@ -209,8 +209,13 @@ static int a5psw_port_enable(struct dsa_switch *ds, int port,
> static int a5psw_port_change_mtu(struct dsa_switch *ds, int port, int new_mtu)
> {
> struct a5psw *a5psw = ds->priv;
> + struct a5psw_of_data *of_data = a5psw->of_data;
[Severity: Low]
Does this assignment cause a compiler warning for discarding qualifiers?
In struct a5psw, of_data is defined as const:
struct a5psw {
...
const struct a5psw_of_data *of_data;
...
};
Assigning it to a non-const local pointer here causes a -Wdiscarded-qualifiers
warning, which might break builds that treat warnings as errors. Should this
local pointer be declared as const?
> +
> + if (dsa_is_cpu_port(ds, port) && of_data->management_port_fixed_frame_len)
> + return 0;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261001154326.754314-1-prabhakar.mahadev-lad.rj@bp.renesas.com?part=10
next prev parent reply other threads:[~2026-10-03 1:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 15:43 [PATCH net-next v2 00/12] Add ETHSW support for Renesas RZ/T2H and RZ/N2H SoCs Prabhakar
2026-10-01 15:43 ` [PATCH net-next v2 01/12] net: dsa: tag_rzn1_a5psw: Drop redundant ETH_P_DSA_A5PSW definition Prabhakar
2026-10-01 15:43 ` [PATCH net-next v2 02/12] net: dsa: tag_rzn1_a5psw: Add RZ/T2H ETHSW tag protocol support Prabhakar
2026-10-01 15:43 ` [PATCH net-next v2 03/12] net: dsa: Kconfig: Expand config description to cover RZ/T2H and RZ/N2H ETHSW Prabhakar
2026-10-01 15:43 ` [PATCH net-next v2 04/12] dt-bindings: net: dsa: renesas,rzn1-a5psw: Add RZ/T2H and RZ/N2H ETHSW support Prabhakar
2026-10-03 1:33 ` sashiko-bot
2026-10-01 15:43 ` [PATCH net-next v2 05/12] net: dsa: rzn1-a5psw: Add support for optional reset control Prabhakar
2026-10-01 15:43 ` [PATCH net-next v2 06/12] net: dsa: rzn1-a5psw: Add support for optional timestamp clock Prabhakar
2026-10-01 15:43 ` [PATCH net-next v2 07/12] net: dsa: rzn1-a5psw: Make use dev_err_probe() Prabhakar
2026-10-01 15:43 ` [PATCH net-next v2 08/12] net: dsa: rzn1-a5psw: Get switch info via OF data Prabhakar
2026-10-01 15:43 ` [PATCH net-next v2 09/12] net: dsa: rzn1-a5psw: Choose tagging protocol based on compatible string Prabhakar
2026-10-01 15:43 ` [PATCH net-next v2 10/12] net: dsa: rzn1-a5psw: Add fixed frame length workaround for management port Prabhakar
2026-10-03 1:33 ` sashiko-bot [this message]
2026-10-09 1:44 ` Jakub Kicinski
2026-10-01 15:43 ` [PATCH net-next v2 11/12] net: dsa: rzn1-a5psw: Add support for RZ/T2H Ethernet switch Prabhakar
2026-10-01 15:43 ` [PATCH net-next v2 12/12] net: dsa: Kconfig: Enable support for RZ/T2H and RZ/N2H SoCs Prabhakar
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=20261003013311.C246A1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.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