From: David Miller <davem@davemloft.net>
To: sathya.perla@emulex.com
Cc: netdev@vger.kernel.org
Subject: Re: [net-next PATCH] be2net: add descriptions for stat counters reported via ethtool
Date: Wed, 01 Feb 2012 14:25:22 -0500 (EST) [thread overview]
Message-ID: <20120201.142522.908710587550609261.davem@davemloft.net> (raw)
In-Reply-To: <1327904259-14583-1-git-send-email-sathya.perla@emulex.com>
From: Sathya Perla <sathya.perla@emulex.com>
Date: Mon, 30 Jan 2012 11:47:39 +0530
> Also rename a few counters appropritely and delete 2 counters that are not
> implemented in HW.
>
> vlan_mismatch_drops does not exist in BE3 and is accounted for in
> address_mismatch_drops. Do the same thing for BE2 and Lancer.
>
> Signed-off-by: Sathya Perla <sathya.perla@emulex.com>
Applied, thanks.
prev parent reply other threads:[~2012-02-01 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 6:17 [net-next PATCH] be2net: add descriptions for stat counters reported via ethtool Sathya Perla
2012-02-01 19:25 ` David Miller [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=20120201.142522.908710587550609261.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sathya.perla@emulex.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).