From: patchwork-bot+netdevbpf@kernel.org
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, richardcochran@gmail.com,
linux@armlinux.org.uk, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: dsa: microchip: fix writes to phy registers >= 0x10
Date: Fri, 23 Jun 2023 02:50:26 +0000 [thread overview]
Message-ID: <168748862638.32034.4855934302738922357.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230620113855.733526-1-linux@rasmusvillemoes.dk>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 20 Jun 2023 13:38:51 +0200 you wrote:
> Patch 1 is just a simplification, technically unrelated to the other
> two patches. But it would be a bit inconsistent to have the new
> ksz_prmw32() introduced in patch 2 use ksz_rmw32() while leaving
> ksz_prmw8() as-is.
>
> The actual fix is of course patch 3. I can definitely see some weird
> behaviour on our ksz9567 when writing to phy registers 0x1e and 0x1f
> (with phytool from userspace), though it does not seem that the effect
> is always to write zeroes to the buddy register as the errata sheet
> says would be the case. In our case, the switch is connected via i2c;
> I hope somebody with other switches and/or the SPI variants can test
> this.
>
> [...]
Here is the summary with links:
- [net-next,1/3] net: dsa: microchip: simplify ksz_prmw8()
https://git.kernel.org/netdev/net-next/c/3b42fbd59511
- [net-next,2/3] net: dsa: microchip: add ksz_prmw32() helper
https://git.kernel.org/netdev/net-next/c/ece28ecbec9f
- [net-next,3/3] net: dsa: microchip: fix writes to phy registers >= 0x10
https://git.kernel.org/netdev/net-next/c/5c844d57aa78
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-06-23 2:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 11:38 [PATCH net-next 0/3] net: dsa: microchip: fix writes to phy registers >= 0x10 Rasmus Villemoes
2023-06-20 11:38 ` [PATCH net-next 1/3] net: dsa: microchip: simplify ksz_prmw8() Rasmus Villemoes
2023-06-20 16:04 ` Simon Horman
2023-06-22 3:48 ` Arun.Ramadoss
2023-06-20 11:38 ` [PATCH net-next 2/3] net: dsa: microchip: add ksz_prmw32() helper Rasmus Villemoes
2023-06-20 16:14 ` Simon Horman
2023-06-22 3:49 ` Arun.Ramadoss
2023-06-20 11:38 ` [PATCH net-next 3/3] net: dsa: microchip: fix writes to phy registers >= 0x10 Rasmus Villemoes
2023-06-20 16:14 ` Simon Horman
2023-06-20 19:28 ` Andrew Lunn
2023-06-21 11:37 ` Rasmus Villemoes
2023-06-23 2: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=168748862638.32034.4855934302738922357.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=woojung.huh@microchip.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).