From: patchwork-bot+netdevbpf@kernel.org
To: Chris Healy <cphealy@gmail.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, neil.armstrong@linaro.org,
khilman@baylibre.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
jeremy.wang@amlogic.com, healych@amazon.com
Subject: Re: [PATCH v3] net: phy: meson-gxl: Add generic dummy stubs for MMD register access
Date: Wed, 01 Feb 2023 05:20:18 +0000 [thread overview]
Message-ID: <167522881803.32169.10037943725132569260.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230130231402.471493-1-cphealy@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Jan 2023 15:14:02 -0800 you wrote:
> From: Chris Healy <healych@amazon.com>
>
> The Meson G12A Internal PHY does not support standard IEEE MMD extended
> register access, therefore add generic dummy stubs to fail the read and
> write MMD calls. This is necessary to prevent the core PHY code from
> erroneously believing that EEE is supported by this PHY even though this
> PHY does not support EEE, as MMD register access returns all FFFFs.
>
> [...]
Here is the summary with links:
- [v3] net: phy: meson-gxl: Add generic dummy stubs for MMD register access
https://git.kernel.org/netdev/net/c/afc2336f89dc
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-02-01 5:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 23:14 [PATCH v3] net: phy: meson-gxl: Add generic dummy stubs for MMD register access Chris Healy
2023-01-31 10:05 ` Jerome Brunet
2023-01-31 10:38 ` Heiner Kallweit
2023-01-31 10:59 ` Jerome Brunet
2023-01-31 12:08 ` Heiner Kallweit
2023-02-01 5:20 ` 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=167522881803.32169.10037943725132569260.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=cphealy@gmail.com \
--cc=davem@davemloft.net \
--cc=healych@amazon.com \
--cc=hkallweit1@gmail.com \
--cc=jeremy.wang@amlogic.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=neil.armstrong@linaro.org \
--cc=netdev@vger.kernel.org \
/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