linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Golle <daniel@makrotopia.org>
Cc: chester.a.unal@arinc9.com, andrew@lunn.ch, olteanv@gmail.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, matthias.bgg@gmail.com,
	angelogioacchino.delregno@collabora.com, lynxis@fe80.eu,
	hkallweit1@gmail.com, linux@armlinux.org.uk,
	rmk+kernel@armlinux.org.uk, sean.wang@mediatek.com,
	Landen.Chao@mediatek.com, f.fainelli@gmail.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net v2 0/6] net: dsa: mt7530: fix remaining swallowed MDIO access errors
Date: Fri, 07 Aug 2026 23:50:38 +0000	[thread overview]
Message-ID: <178614663864.2467553.3447104731237010807.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1785811140.git.daniel@makrotopia.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 4 Aug 2026 04:10:17 +0100 you wrote:
> The original series, "net: dsa: mt7530: fix swallowed MDIO read
> errors", landed on net as its v1 [1] just before its v2 [2] was sent.
> This series started from the fixes in that original v2 which its v1
> had not already carried: the two standalone patches that original v2
> grew from the Sashiko AI review of its v1 (the mtk-lynxi read check
> and the regmap IRQ serialization), plus, split into patches of their
> own, the companion fixes original v2 had folded into the
> already-applied patches -- the unchecked bus->read() in core_rmw() and
> the unchecked PHY_IAC command writes in the MT7531 indirect PHY access
> functions.
> 
> [...]

Here is the summary with links:
  - [net,v2,1/6] net: pcs: mtk-lynxi: check regmap reads in mtk_pcs_lynxi_get_state()
    https://git.kernel.org/netdev/net-next/c/5cc65c01cdc5
  - [net,v2,2/6] net: dsa: mt7530: check bus->read() error in core_rmw()
    https://git.kernel.org/netdev/net-next/c/573d6e3afe3d
  - [net,v2,3/6] net: dsa: mt7530: error out on failed PHY_IAC command writes
    https://git.kernel.org/netdev/net-next/c/1c95dcb7e923
  - [net,v2,4/6] net: dsa: mt7530: check CORE_PLL_GROUP4 access in mt7531_setup()
    https://git.kernel.org/netdev/net-next/c/1ae63b018d3d
  - [net,v2,5/6] net: dsa: mt7530: check command register writes in fdb and vlan cmd
    https://git.kernel.org/netdev/net-next/c/f67b0bae07fe
  - [net,v2,6/6] net: dsa: mt7530: serialize the regmap IRQ chip like every other user
    https://git.kernel.org/netdev/net-next/c/dd52b3df25ed

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-07 23:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04  3:10 [PATCH net v2 0/6] net: dsa: mt7530: fix remaining swallowed MDIO access errors Daniel Golle
2026-08-04  3:10 ` [PATCH net v2 1/6] net: pcs: mtk-lynxi: check regmap reads in mtk_pcs_lynxi_get_state() Daniel Golle
2026-08-04  3:10 ` [PATCH net v2 2/6] net: dsa: mt7530: check bus->read() error in core_rmw() Daniel Golle
2026-08-04  3:10 ` [PATCH net v2 3/6] net: dsa: mt7530: error out on failed PHY_IAC command writes Daniel Golle
2026-08-04  3:10 ` [PATCH net v2 4/6] net: dsa: mt7530: check CORE_PLL_GROUP4 access in mt7531_setup() Daniel Golle
2026-08-04  3:10 ` [PATCH net v2 5/6] net: dsa: mt7530: check command register writes in fdb and vlan cmd Daniel Golle
2026-08-04  3:11 ` [PATCH net v2 6/6] net: dsa: mt7530: serialize the regmap IRQ chip like every other user Daniel Golle
2026-08-07 23:50 ` patchwork-bot+netdevbpf [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=178614663864.2467553.3447104731237010807.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Landen.Chao@mediatek.com \
    --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=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --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=lynxis@fe80.eu \
    --cc=matthias.bgg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=sean.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).