From: Ben Hutchings <bhutchings@solarflare.com>
To: netdev <netdev@vger.kernel.org>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Leonardo Potenza <leonardo.potenza@intel.com>
Subject: ethtool 3.12 released
Date: Fri, 8 Nov 2013 17:21:26 +0000 [thread overview]
Message-ID: <1383931286.3802.28.camel@bwh-desktop.uk.level5networks.com> (raw)
ethtool version 3.12.1 has been released.
This includes a couple of changes that should have gone into 3.12.
Home page: https://ftp.kernel.org/pub/software/network/ethtool/
Download link:
https://ftp.kernel.org/pub/software/network/ethtool/ethtool-3.12.1.tar.xz
Release notes:
* Fix: Memory corruption when applying external calibration to
SFF-8472 module diagnostics (-m option)
* Feature: Add Intel 82599 and x540 DCB registers to dump
(-d option)
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next reply other threads:[~2013-11-08 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 17:21 Ben Hutchings [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-07 19:56 ethtool 3.12 released Ben Hutchings
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=1383931286.3802.28.camel@bwh-desktop.uk.level5networks.com \
--to=bhutchings@solarflare.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=leonardo.potenza@intel.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