From: "John W. Linville" <linville@tuxdriver.com>
To: netdev@vger.kernel.org
Subject: ethtool 5.6 released
Date: Tue, 12 May 2020 11:10:51 -0400 [thread overview]
Message-ID: <20200512151051.GC615364@tuxdriver.com> (raw)
ethtool version 5.6 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.6.tar.xz
Release notes:
* Feature: add --debug option to control debugging messages
* Feature: use named initializers in command line option list
* Feature: netlink: add netlink related UAPI header files
* Feature: netlink: introduce the netlink interface
* Feature: netlink: message buffer and composition helpers
* Feature: netlink: netlink socket wrapper and helpers
* Feature: netlink: initialize ethtool netlink socket
* Feature: netlink: add support for string sets
* Feature: netlink: add notification monitor
* Feature: netlink: add bitset helpers
* Feature: netlink: partial netlink handler for gset (no option)
* Feature: netlink: support getting wake-on-lan and debugging settings
* Feature: netlink: add basic command line parsing helpers
* Feature: netlink: add bitset command line parser handlers
* Feature: netlink: add netlink handler for sset (-s)
* Feature: netlink: support tests with netlink enabled
* Feature: netlink: add handler for permaddr (-P)
* Feature: netlink: support for pretty printing netlink messages
* Feature: netlink: message format description for ethtool netlink
* Feature: netlink: message format descriptions for genetlink control
* Feature: netlink: message format descriptions for rtnetlink
* Feature: netlink: use pretty printing for ethtool netlink messages
John
P.S. If you are interested in maintaining ethtool, please let me know!
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
reply other threads:[~2020-05-12 15:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200512151051.GC615364@tuxdriver.com \
--to=linville@tuxdriver.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).