From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QWx2aW4gxaBpcHJhZ2EgPGFsdmluQHBxcnMuZGs+?=@ci.codeaurora.org
Cc: linus.walleij@linaro.org, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org,
mir@bang-olufsen.dk, alsi@bang-olufsen.dk, luizluca@gmail.com,
arinc.unal@arinc9.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] net: dsa: realtek: fix PHY register read corruption
Date: Wed, 23 Feb 2022 12:30:11 +0000 [thread overview]
Message-ID: <164561941143.20664.9166640246094519424.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220221184631.252308-1-alvin@pqrs.dk>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 21 Feb 2022 19:46:29 +0100 you wrote:
> From: Alvin Šipraga <alsi@bang-olufsen.dk>
>
> These two patches fix the issue reported by Arınç where PHY register
> reads sometimes return garbage data.
>
> v1 -> v2:
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] net: dsa: realtek: allow subdrivers to externally lock regmap
https://git.kernel.org/netdev/net-next/c/907e772f6f6d
- [v2,net-next,2/2] net: dsa: realtek: rtl8365mb: serialize indirect PHY register access
https://git.kernel.org/netdev/net-next/c/2796728460b8
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:[~2022-02-23 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 18:46 [PATCH v2 net-next 0/2] net: dsa: realtek: fix PHY register read corruption Alvin Šipraga
2022-02-21 18:46 ` [PATCH v2 net-next 1/2] net: dsa: realtek: allow subdrivers to externally lock regmap Alvin Šipraga
2022-02-21 19:06 ` Vladimir Oltean
2022-02-21 18:46 ` [PATCH v2 net-next 2/2] net: dsa: realtek: rtl8365mb: serialize indirect PHY register access Alvin Šipraga
2022-02-21 19:09 ` Vladimir Oltean
2022-02-21 23:21 ` Linus Walleij
2022-02-22 0:19 ` Alvin Šipraga
2022-02-22 15:14 ` Linus Walleij
2022-02-22 16:06 ` Alvin Šipraga
2022-02-23 12:30 ` 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=164561941143.20664.9166640246094519424.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?QWx2aW4gxaBpcHJhZ2EgPGFsdmluQHBxcnMuZGs+?=@ci.codeaurora.org \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=arinc.unal@arinc9.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=mir@bang-olufsen.dk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.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