From: Ben Hutchings <ben@decadent.org.uk>
To: Shrikrishna Khare <skhare@vmware.com>,
bwh@kernel.org, netdev@vger.kernel.org, pv-drivers@vmware.com
Cc: Bhavesh Davda <bhavesh@vmware.com>
Subject: Re: [PATCH] ethtool: Add vmxnet3 register dump support
Date: Fri, 09 Oct 2015 03:21:00 +0100 [thread overview]
Message-ID: <1444357260.2956.289.camel@decadent.org.uk> (raw)
In-Reply-To: <1443046752-28892-1-git-send-email-skhare@vmware.com>
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
On Wed, 2015-09-23 at 15:19 -0700, Shrikrishna Khare wrote:
> This adds support for dumping vmxnet3 registers in a readable format.
>
> Signed-off-by: Shrikrishna Khare <skhare@vmware.com>
> Signed-off-by: Bhavesh Davda <bhavesh@vmware.com>
> Acked-by: Srividya Murali <smurali@vmware.com>
[...]
Applied, thanks.
Ben.
--
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
prev parent reply other threads:[~2015-10-09 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 22:19 [PATCH] ethtool: Add vmxnet3 register dump support Shrikrishna Khare
2015-10-09 2:21 ` Ben Hutchings [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=1444357260.2956.289.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=bhavesh@vmware.com \
--cc=bwh@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=skhare@vmware.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).