mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: kyle.switch@motor-comm.com
Cc: Jakub Kicinski <kuba@kernel.org>,
	andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, mmyangfl@gmail.com,
	horms@kernel.org, linux@armlinux.org.uk, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, ming.xu@motor-comm.com,
	xiaolin.xu@motor-comm.com, jianmin.wang@motor-comm.com,
	wei.zhang@gl-inet.com, sijia.huang@gl-inet.com
Subject: Re: [PATCH net-next v17 3/5] net: dsa: motorcomm: use fixed-width GENMASK_U*() helpers
Date: Tue, 10 Nov 2026 15:26:52 -0800	[thread overview]
Message-ID: <20261110232652.2437155-1-kuba@kernel.org> (raw)
In-Reply-To: <20261105031442.4164960-4-kyle.switch@motor-comm.com>

This is an AI-generated review of your patch. The human sending this
email has considered the AI review valid, or at least plausible.
---
net: dsa: motorcomm: use fixed-width GENMASK_U*() helpers

This patch replaces two GENMASK() uses in the motorcomm DSA driver with
GENMASK_U32(). One is in yt921x_chip_setup_dsa() in chip.c and the other
is in yt921x_mbus_int_init() in mdio_bus.c. It is described as a type
cleanup with no functional change.

> Some masks assigned to u16 and u32 fields are defined with
> GENMASK(),which is an unsigned long constant and wider than
> the field type on 64-bit builds. Convert the YT921X_MBUS_CTRL_*
> masks used by mdio_bus.c to fixed-width helpers.
>
> This is a type cleanup only, with no functional change. Other
> GENMASK() uses in the driver are intentionally left untouched.

[Severity: Medium]
Does this description match the diff? The patch doesn't seem to touch
the YT921X_MBUS_CTRL_* masks at all. After this patch they are still
plain GENMASK() in drivers/net/dsa/motorcomm/mdio_bus.h:

#define  YT921X_MBUS_CTRL_PORT_M		GENMASK(25, 21)
#define  YT921X_MBUS_CTRL_REG_M			GENMASK(20, 16)
#define  YT921X_MBUS_CTRL_TYPE_M		GENMASK(11, 8)  /* wild guess */
#define  YT921X_MBUS_CTRL_OP_M			GENMASK(3, 2)  /* wild guess */

They still feed the u32 mask variables in yt921x_intif_read(),
yt921x_intif_write(), yt921x_extif_read() and yt921x_extif_write(),
for example:

	mask = YT921X_MBUS_CTRL_PORT_M | YT921X_MBUS_CTRL_REG_M |
	       YT921X_MBUS_CTRL_OP_M;

No later patch in the series converts them either.

The two lines the patch does change are not MBUS_CTRL masks. In
yt921x_chip_setup_dsa(), the mask written to YT921X_FILTER_UNK_UCAST
and YT921X_FILTER_UNK_MCAST is changed:

	ctrl = GENMASK_U32(10, 0);

That seems to contradict "Other GENMASK() uses in the driver are
intentionally left untouched".

The other change is the phy_mask calculation in yt921x_mbus_int_init():

	mbus->phy_mask = ~GENMASK_U32(max_ports - 1, 0);

Also, the message refers to "masks assigned to u16 and u32 fields",
but none of the changed lines involve a u16 field.

Both changed lines give the same values as before, so runtime behaviour
does not change. Only the description is off.

Could the message be reworded to describe the FILTER_UNK and phy_mask
changes, with the "left untouched" sentence dropped? The other option
is to convert the YT921X_MBUS_CTRL_* masks in mdio_bus.h as the
message says.

  reply	other threads:[~2026-11-10 23:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  3:14 [PATCH net-next v17 0/5] net: dsa: motorcomm: add support yt922x driver Kyle Switch
2026-11-05  3:14 ` [PATCH net-next v17 1/5] net: dsa: motorcomm: initialize dsa_switch based on chipid Kyle Switch
2026-11-10 23:26   ` Jakub Kicinski
2026-11-05  3:14 ` [PATCH net-next v17 2/5] net: dsa: motorcomm: use max_ports in series for port bounds checking Kyle Switch
2026-11-05  3:14 ` [PATCH net-next v17 3/5] net: dsa: motorcomm: use fixed-width GENMASK_U*() helpers Kyle Switch
2026-11-10 23:26   ` Jakub Kicinski [this message]
2026-11-05  3:14 ` [PATCH net-next v17 4/5] net: dsa: tag_yt922x: add support for Motorcomm YT922x tags Kyle Switch
2026-11-05  3:14 ` [PATCH net-next v17 5/5] net: dsa: motorcomm: Add support for Motorcomm YT922x Kyle Switch
2026-11-10 23:26   ` Jakub Kicinski

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=20261110232652.2437155-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jianmin.wang@motor-comm.com \
    --cc=kyle.switch@motor-comm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=ming.xu@motor-comm.com \
    --cc=mmyangfl@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=sijia.huang@gl-inet.com \
    --cc=wei.zhang@gl-inet.com \
    --cc=xiaolin.xu@motor-comm.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®