From: patchwork-bot+netdevbpf@kernel.org
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: netdev@vger.kernel.org, jeffd@silicom-usa.com,
kernel.org-fo5k2w@ycharbi.fr
Subject: Re: [PATCH net] Revert "ixgbe: Manual AN-37 for troublesome link partners for X550 SFI"
Date: Thu, 23 May 2024 09:00:29 +0000 [thread overview]
Message-ID: <171645482956.18839.2859960511467827703.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240520-net-2024-05-20-revert-silicom-switch-workaround-v1-1-50f80f261c94@intel.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 20 May 2024 17:21:27 -0700 you wrote:
> This reverts commit 565736048bd5f9888990569993c6b6bfdf6dcb6d.
>
> According to the commit, it implements a manual AN-37 for some
> "troublesome" Juniper MX5 switches. This appears to be a workaround for a
> particular switch.
>
> It has been reported that this causes a severe breakage for other switches,
> including a Cisco 3560CX-12PD-S.
>
> [...]
Here is the summary with links:
- [net] Revert "ixgbe: Manual AN-37 for troublesome link partners for X550 SFI"
https://git.kernel.org/netdev/net/c/b35b1c0b4e16
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:[~2024-05-23 9:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 0:21 [PATCH net] Revert "ixgbe: Manual AN-37 for troublesome link partners for X550 SFI" Jacob Keller
2024-05-21 16:41 ` Simon Horman
2024-05-21 16:49 ` Jeff Daly
2024-05-21 17:12 ` kernel.org-fo5k2w
2024-05-21 21:05 ` Jacob Keller
2024-05-23 16:15 ` Jacob Keller
2024-05-23 16:18 ` Jeff Daly
2024-05-23 16:49 ` kernel.org-fo5k2w
2024-05-23 18:47 ` Jacob Keller
2024-05-23 18:49 ` Jacob Keller
2024-05-23 20:19 ` kernel.org-fo5k2w
2024-05-23 20:35 ` Jacob Keller
2024-06-26 14:30 ` Jeff Daly
2024-05-23 9:00 ` 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=171645482956.18839.2859960511467827703.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jeffd@silicom-usa.com \
--cc=kernel.org-fo5k2w@ycharbi.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.