From: "Joris Vaišvila" <joey@tinyisr.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, nbd@nbd.name, sean.wang@mediatek.com,
lorenzo@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH v2] net: ethernet: mtk_eth_soc: avoid writing to ESW registers on MT7628
Date: Fri, 9 Jan 2026 22:09:49 +0200 [thread overview]
Message-ID: <aWE9Nt0bmXpRCPAT@plutus> (raw)
In-Reply-To: <20260108083530.6169b627@kernel.org>
Hi Simon and Jakub,
Thank you for the review.
> registering alternate phy ops for MT7628. This would push the conditional
> handling to probe rather than calback execution time. And I suspect it
> would lead to a cleaner implementation.
I wanted to keep the fix minimal and overlooked this as a potential
solution. This will make the next revision way easier to follow.
> Plus the commit message says: "Existing drivers never use the affected
> features, so this went unnoticed." which makes it sound like user will
> not notice the bad writes today?
>
> So perhaps we can go for the cleaner approach and stick to net-next
> (without fixing the older kernels?). Sorry for not reading the commit
> message closely enough on v1.
Yes, current users should not be affected by the bug. I only ran into it
while kernel hacking. The fix is not necessary to add to older kernels.
Following your suggestions, v3 will target net-next and use separate phy
ops for clarity.
prev parent reply other threads:[~2026-01-09 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 5:18 [PATCH v2] net: ethernet: mtk_eth_soc: avoid writing to ESW registers on MT7628 Joris Vaisvila
2026-01-08 15:04 ` Simon Horman
2026-01-08 16:35 ` Jakub Kicinski
2026-01-09 20:09 ` Joris Vaišvila [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=aWE9Nt0bmXpRCPAT@plutus \
--to=joey@tinyisr.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.