From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
marex@denx.de, kernel@pengutronix.de,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
netdev@vger.kernel.org
Subject: Re: [PATCH net v1 1/1] net: phy: micrel: correct KSZ9131RNX EEE capabilities and advertisement
Date: Mon, 27 Mar 2023 07:20:18 +0000 [thread overview]
Message-ID: <167990161814.4487.3157195174549060805.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230324133908.2145226-1-o.rempel@pengutronix.de>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 24 Mar 2023 14:39:08 +0100 you wrote:
> The KSZ9131RNX incorrectly shows EEE capabilities in its registers.
> Although the "EEE control and capability 1" (Register 3.20) is set to 0,
> indicating no EEE support, the "EEE advertisement 1" (Register 7.60) is
> set to 0x6, advertising EEE support for 1000BaseT/Full and
> 100BaseT/Full.
> This inconsistency causes PHYlib to assume there is no EEE support,
> preventing control over EEE advertisement, which is enabled by default.
>
> [...]
Here is the summary with links:
- [net,v1,1/1] net: phy: micrel: correct KSZ9131RNX EEE capabilities and advertisement
https://git.kernel.org/netdev/net/c/f2e9d083f768
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-03-27 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 13:39 [PATCH net v1 1/1] net: phy: micrel: correct KSZ9131RNX EEE capabilities and advertisement Oleksij Rempel
2023-03-27 7: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=167990161814.4487.3157195174549060805.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.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