From: Florian Fainelli <f.fainelli@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>, netdev@vger.kernel.org
Cc: Michal Kubecek <mkubecek@suse.cz>, davem@davemloft.net
Subject: Re: ethtool 5.7 released
Date: Thu, 4 Jun 2020 13:15:58 -0700 [thread overview]
Message-ID: <33d31995-45fc-cf65-9af3-9cf9698dd554@gmail.com> (raw)
In-Reply-To: <20200604183539.GC1408312@tuxdriver.com>
On 6/4/2020 11:35 AM, John W. Linville wrote:
> ethtool version 5.7 has been released.
>
> Home page: https://www.kernel.org/pub/software/network/ethtool/
> Download link:
> https://www.kernel.org/pub/software/network/ethtool/ethtool-5.7.tar.xz
>
> Release notes:
>
> * Feature: ethtool: Add support for Low Latency Reed Solomon
> * Fix: ethtool.c: Report transceiver correctly
> * Feature: features: accept long legacy flag names when setting features
> * Feature: refactor interface between ioctl and netlink code
> * Feature: netlink: use genetlink ops information to decide about fallback
> * Feature: netlink: show netlink error even without extack
> * Feature: ethtool: add support for newer SFF-8024 compliance codes
> * Feature: Rewrite printf() due to -Werror=format-security
>
> This should be my last release as maintainer of ethtool. Michal
> Kubecek has graciously agreed to take-on that responsibility, and I
> have every confidence that he will do a great job in that capacity
> for our community.
>
> Thanks, Michal!
Thank you John for maintaining ethtool for the past few years and thanks
Michal for stepping up.
--
Florian
next prev parent reply other threads:[~2020-06-04 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 18:35 ethtool 5.7 released John W. Linville
2020-06-04 20:15 ` Florian Fainelli [this message]
2020-06-04 23:01 ` David Miller
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=33d31995-45fc-cf65-9af3-9cf9698dd554@gmail.com \
--to=f.fainelli@gmail.com \
--cc=davem@davemloft.net \
--cc=linville@tuxdriver.com \
--cc=mkubecek@suse.cz \
--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).