From: patchwork-bot+netdevbpf@kernel.org
To: Sverdlin@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Alexander <alexander.sverdlin@siemens.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
olek2@wp.pl, daniel@makrotopia.org, john@phrozen.org,
hauke@hauke-m.de, stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: phy: intel-xway: workaround 100BASE-TX Link-Up issue
Date: Thu, 24 Sep 2026 17:30:14 +0000 [thread overview]
Message-ID: <179027101415.1669750.10138214734106545986.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260922075251.23386-1-alexander.sverdlin@siemens.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 22 Sep 2026 09:52:46 +0200 you wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> MaxLinear GSW12x/GSW14x Ethernet Switch Errata Sheet states:
> "An issue has been sporadically observed after device power-on on the first
> link-up attempt in 100BASE-TX mode resulting in either the link-up taking a
> long time, or failing to link-up altogether...
>
> [...]
Here is the summary with links:
- [net,v2] net: phy: intel-xway: workaround 100BASE-TX Link-Up issue
https://git.kernel.org/netdev/net/c/b94773dc4df7
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:[~2026-09-24 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 7:52 A. Sverdlin
2026-09-22 12:22 ` Andrew Lunn
2026-09-23 22:55 ` netdev-bot+sashiko
2026-09-24 7:58 ` Sverdlin, Alexander
2026-09-24 17: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=179027101415.1669750.10138214734106545986.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Sverdlin@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=alexander.sverdlin@siemens.com \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hauke@hauke-m.de \
--cc=hkallweit1@gmail.com \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=pabeni@redhat.com \
--cc=stable@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
all inboxes | Powered by JetHome®