From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net, Ben Hutchings <ben@decadent.org.uk>
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com
Subject: Re: [ethtool 0/3][pull request] Intel Wired LAN Driver Updates 2016-05-03
Date: Tue, 24 May 2016 16:47:11 -0700 [thread overview]
Message-ID: <1464133631.2631.35.camel@intel.com> (raw)
In-Reply-To: <1462380293-4132-1-git-send-email-jeffrey.t.kirsher@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
On Wed, 2016-05-04 at 09:44 -0700, Jeff Kirsher wrote:
> This series contains updates to ixgbe in ethtool.
>
> Preethi adds missing device IDs and mac_type definitions, also updated
> the display registers for x550, x550em_x/a. Cleaned up the format string
> storage by taking advantage of "for" loops.
>
> The following are changes since commit
> deb1c6613ec14fd828d321e38c7bea45fe559bd5:
> Release version 4.5.
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/ethtool master
>
> Preethi Banala (3):
> ethtool/ixgbe: Add device ID and mac_type definitions
> ethtool/ixgbe: Correct offsets and support x550, x550em_x, x550em_a
> ethtool/ixgbe: Reduce format string storage
>
> ixgbe.c | 173 +++++++++++++++++++++++++++++++++++-----------------------
> ------
> 1 file changed, 95 insertions(+), 78 deletions(-)
>
Is Ben still maintaining ethtool? I ask because I have this series which I
sent out earlier this month, with no word and I know there is at least one
other ethtool patch series that has had no response or committal from who
ever is maintaining ethtool.
I know we discussed last netconf that we should look at possibly a new tool
to address the shortcomings of ethtool, but I was not aware we had
abandoned maintaining the current ethtool already before any replacement
tool has been developed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-24 23:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 16:44 [ethtool 0/3][pull request] Intel Wired LAN Driver Updates 2016-05-03 Jeff Kirsher
2016-05-04 16:44 ` [ethtool 1/3] ethtool/ixgbe: Add device ID and mac_type definitions Jeff Kirsher
2016-05-04 16:44 ` [ethtool 2/3] ethtool/ixgbe: Correct offsets and support x550, x550em_x, x550em_a Jeff Kirsher
2016-05-04 16:44 ` [ethtool 3/3] ethtool/ixgbe: Reduce format string storage Jeff Kirsher
2016-05-16 23:46 ` [ethtool 0/3][pull request] Intel Wired LAN Driver Updates 2016-05-03 Jeff Kirsher
2016-05-24 23:47 ` Jeff Kirsher [this message]
2016-05-25 14:12 ` Ben Hutchings
2016-06-26 9:04 ` 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=1464133631.2631.35.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.com \
/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).