From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: "Vick, Matthew" <matthew.vick@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"gospo@redhat.com" <gospo@redhat.com>,
"sassmann@redhat.com" <sassmann@redhat.com>
Subject: Re: [ethtool] ethtool: Correct register dump offsets for Intel 82575 chipsets.
Date: Thu, 12 Jan 2012 06:35:34 -0800 [thread overview]
Message-ID: <1326378934.2709.64.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1326377284.2819.7.camel@deadeye>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
On Thu, 2012-01-12 at 14:08 +0000, Ben Hutchings wrote:
> On Thu, 2012-01-12 at 05:11 -0800, Jeff Kirsher wrote:
> > On Fri, 2011-12-23 at 02:32 -0800, Kirsher, Jeffrey T wrote:
> > > From: Matthew Vick <matthew.vick@intel.com>
> > >
> > > When support was added to dump the registers on 82575 chipset devices,
> > > six register offsets (receive/transmit desc length, head, and tail)
> > > were incorrectly mapped. This patch remaps the offsets to the correct
> > > registers.
> [...]
> > Ben, what is the status of this patch?
>
> The status is 'arrived just as I went on vacation, and forgotten'.
:)
>
> I'll be sure to apply this before releasing ethtool 3.2.
Thanks Ben!
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-01-12 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 10:32 [ethtool] ethtool: Correct register dump offsets for Intel 82575 chipsets Jeff Kirsher
2012-01-12 13:11 ` Jeff Kirsher
2012-01-12 14:08 ` Ben Hutchings
2012-01-12 14:35 ` Jeff Kirsher [this message]
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=1326378934.2709.64.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=bhutchings@solarflare.com \
--cc=gospo@redhat.com \
--cc=matthew.vick@intel.com \
--cc=netdev@vger.kernel.org \
--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