public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Russell King (Oracle) <rmk+kernel@armlinux•org.uk>
Cc: andrew@lunn•ch, hkallweit1@gmail•com,
	Raju.Lakkaraju@microchip•com, davem@davemloft•net,
	edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
	netdev@vger•kernel.org
Subject: Re: [PATCH net] net: phylink: actually fix ksettings_set() ethtool call
Date: Sat, 03 Jun 2023 07:00:21 +0000	[thread overview]
Message-ID: <168577562193.13767.8075188819836108856.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <E1q4eLm-00Ayxk-GZ@rmk-PC.armlinux.org.uk>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:

On Thu, 01 Jun 2023 10:12:06 +0100 you wrote:
> Raju Lakkaraju reported that the below commit caused a regression
> with Lan743x drivers and a 2.5G SFP. Sadly, this is because the commit
> was utterly wrong. Let's fix this properly by not moving the
> linkmode_and(), but instead copying the link ksettings and then
> modifying the advertising mask before passing the modified link
> ksettings to phylib.
> 
> [...]

Here is the summary with links:
  - [net] net: phylink: actually fix ksettings_set() ethtool call
    https://git.kernel.org/netdev/net/c/03c44a21d033

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2023-06-03  7:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01  9:12 [PATCH net] net: phylink: actually fix ksettings_set() ethtool call Russell King (Oracle)
2023-06-03  7:00 ` patchwork-bot+netdevbpf [this message]
2023-06-05  5:34 ` Raju Lakkaraju
  -- strict thread matches above, loose matches on Subject: below --
2023-06-01  9:02 Russell King (Oracle)
2023-06-01  9:05 ` Russell King (Oracle)

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=168577562193.13767.8075188819836108856.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=Raju.Lakkaraju@microchip$(echo .)com \
    --cc=andrew@lunn$(echo .)ch \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=hkallweit1@gmail$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=rmk+kernel@armlinux$(echo .)org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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