From: patchwork-bot+netdevbpf@kernel.org
To: Danielle Ratson <danieller@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
eric.dumazet@gmail.com, andrew@lunn.ch, mkubecek@suse.cz,
f.fainelli@gmail.com, acardace@redhat.com, irusskikh@marvell.com,
gustavo@embeddedor.com, magnus.karlsson@intel.com,
ecree@solarflare.com, idosch@nvidia.com, jiri@nvidia.com,
mlxsw@nvidia.com
Subject: Re: [PATCH net v3 0/2] Fix link_mode derived params functionality
Date: Wed, 07 Apr 2021 22:10:09 +0000 [thread overview]
Message-ID: <161783340982.5631.4957683158409610232.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210407100652.2150415-1-danieller@nvidia.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Wed, 7 Apr 2021 13:06:50 +0300 you wrote:
> Currently, link_mode parameter derives 3 other link parameters, speed,
> lanes and duplex, and the derived information is sent to user space.
>
> Few bugs were found in that functionality.
> First, some drivers clear the 'ethtool_link_ksettings' struct in their
> get_link_ksettings() callback and cause receiving wrong link mode
> information in user space. And also, some drivers can report random
> values in the 'link_mode' field and cause general protection fault.
>
> [...]
Here is the summary with links:
- [net,v3,1/2] ethtool: Remove link_mode param and derive link params from driver
https://git.kernel.org/netdev/net/c/a975d7d8a356
- [net,v3,2/2] ethtool: Add lanes parameter for ETHTOOL_LINK_MODE_10000baseR_FEC_BIT
https://git.kernel.org/netdev/net/c/fde32dbe712b
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:[~2021-04-07 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 10:06 [PATCH net v3 0/2] Fix link_mode derived params functionality Danielle Ratson
2021-04-07 10:06 ` [PATCH net v3 1/2] ethtool: Remove link_mode param and derive link params from driver Danielle Ratson
2021-04-07 10:06 ` [PATCH net v3 2/2] ethtool: Add lanes parameter for ETHTOOL_LINK_MODE_10000baseR_FEC_BIT Danielle Ratson
2021-04-07 22:10 ` 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=161783340982.5631.4957683158409610232.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acardace@redhat.com \
--cc=andrew@lunn.ch \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=eric.dumazet@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gustavo@embeddedor.com \
--cc=idosch@nvidia.com \
--cc=irusskikh@marvell.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=mkubecek@suse.cz \
--cc=mlxsw@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).