From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Golle <daniel@makrotopia.org>
Cc: "Chester A. Unal" <chester.a.unal@arinc9.com>,
Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net-next v4 0/8] net: dsa: mt7530: modernise register access and add two DSA ops
Date: Mon, 27 Jul 2026 16:44:15 -0700 [thread overview]
Message-ID: <20260727164415.7181b193@kernel.org> (raw)
In-Reply-To: <cover.1784481922.git.daniel@makrotopia.org>
On Sun, 19 Jul 2026 18:33:45 +0100 Daniel Golle wrote:
> v4:
> * rebase onto current net-next
> * 5/8: zero the read-back buffer in mt7530_regmap_read() instead of
> initialising the result variables at every call site, as suggested
> by Jakub
> * 6/8: keep MT753X_CTRL_PHY_ADDR() as plain address arithmetic rather
> than converting it to FIELD_PREP() as suggested in review: the macro
> computes the MDIO bus address of the switch PHYs, used as the addr
> argument of bus->read/write and as an iterator base in
> mt7530_setup_mdio(), not a hardware register field
Looks like this needs another rebase
BTW Sashiko is still complaining about corner cases of patch 5:
https://sashiko.dev/#/patchset/16c17477dc9eea8054455ef0e444a687336ced70.1784481922.git.daniel@makrotopia.org
prev parent reply other threads:[~2026-07-27 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 17:33 [PATCH net-next v4 0/8] net: dsa: mt7530: modernise register access and add two DSA ops Daniel Golle
2026-07-19 17:53 ` [PATCH net-next v4 1/8] net: dsa: mt7530: move MDIO bus locking into regmap Daniel Golle
2026-07-19 17:53 ` [PATCH net-next v4 2/8] net: dsa: mt7530: fold mt7530_mii_write/read into mt7530_write/read Daniel Golle
2026-07-19 17:53 ` [PATCH net-next v4 3/8] net: dsa: mt7530: replace mt7530_write with regmap_write Daniel Golle
2026-07-19 17:53 ` [PATCH net-next v4 4/8] net: dsa: mt7530: replace mt7530_rmw/set/clear with regmap API Daniel Golle
2026-07-19 17:53 ` [PATCH net-next v4 5/8] net: dsa: mt7530: replace mt7530_read with regmap_read Daniel Golle
2026-07-19 17:54 ` [PATCH net-next v4 6/8] net: dsa: mt7530: convert to use field accessor macros Daniel Golle
2026-07-19 17:54 ` [PATCH net-next v4 7/8] net: dsa: mt7530: implement port_fast_age Daniel Golle
2026-07-19 17:54 ` [PATCH net-next v4 8/8] net: dsa: mt7530: implement port_change_conduit op Daniel Golle
2026-07-27 23:44 ` Jakub Kicinski [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=20260727164415.7181b193@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chester.a.unal@arinc9.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--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