From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 2/3] ethtool/ixgbe: Correct offsets and support x550, x550em_x, x550em_a
Date: Fri, 22 Apr 2016 20:56:41 +0000 [thread overview]
Message-ID: <26D9FDECA4FBDD4AADA65D8E2FC68A4A0F9D2AB7@ORSMSX104.amr.corp.intel.com> (raw)
In-Reply-To: <20160421182851.13330.71861.stgit@ixgbe-dev.jf.intel.com>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuosl.org] On
> Behalf Of Preethi Banala
> Sent: Thursday, April 21, 2016 11:29 AM
> To: intel-wired-lan at lists.osuosl.org
> Subject: [Intel-wired-lan] [PATCH 2/3] ethtool/ixgbe: Correct offsets and
> support x550, x550em_x, x550em_a
>
> Correct hard-coded wrong offset values and add several conditions to display
> registers for x550, x550em_x and x550em_a based on datasheet/ EAS
> document.
>
> Signed-off-by: Preethi Banala <preethi.banala@intel.com>
> ---
> ixgbe.c | 74 +++++++++++++++++++++++++++++++++++---------------------
> -------
> 1 file changed, 41 insertions(+), 33 deletions(-)
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Ethtool reg dump shows added information and correct offsets
next prev parent reply other threads:[~2016-04-22 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 18:28 [Intel-wired-lan] [PATCH 0/3] Update ethtool utility Preethi Banala
2016-04-21 18:28 ` [Intel-wired-lan] [PATCH 1/3] ethtool/ixgbe: Add device ID and mac_type definitions Preethi Banala
2016-04-22 20:21 ` Bowers, AndrewX
2016-04-21 18:28 ` [Intel-wired-lan] [PATCH 2/3] ethtool/ixgbe: Correct offsets and support x550, x550em_x, x550em_a Preethi Banala
2016-04-22 20:56 ` Bowers, AndrewX [this message]
2016-04-21 18:28 ` [Intel-wired-lan] [PATCH 3/3] ethtool/ixgbe: Reduce format string storage Preethi Banala
2016-04-22 20:57 ` Bowers, AndrewX
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=26D9FDECA4FBDD4AADA65D8E2FC68A4A0F9D2AB7@ORSMSX104.amr.corp.intel.com \
--to=andrewx.bowers@intel.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.