From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: greearb@candelatech.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v4 09/16] e100: Support RXALL feature flag.
Date: Thu, 16 Feb 2012 16:08:07 -0800 [thread overview]
Message-ID: <1329437287.2869.22.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1329418421-31574-2-git-send-email-greearb@candelatech.com>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
On Thu, 2012-02-16 at 10:53 -0800, greearb@candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> This allows the NIC to receive packets with bad FCS
> and other errors. Good for sniffing packets on flakey
> networks.
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
> ---
>
> v4: Only flax rx-over-length errors if pkt is beyond
> maximum expected packet size, not just beyond the MTU.
> This matches the existing logic for this counter.
>
> :100644 100644 6f9f70a... 4d8a616...
> M drivers/net/ethernet/intel/e100.c
> drivers/net/ethernet/intel/e100.c | 22 ++++++++++++++++++++--
> 1 files changed, 20 insertions(+), 2 deletions(-)
Thanks Ben, I will replace the patch that is currently in my queue with
this updated patch.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-17 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 18:53 [PATCH v4 02/16] e100: Support RXFCS feature flag greearb
2012-02-16 18:53 ` [PATCH v4 09/16] e100: Support RXALL " greearb
2012-02-17 0:08 ` Jeff Kirsher [this message]
2012-02-17 0:07 ` [PATCH v4 02/16] e100: Support RXFCS " Jeff Kirsher
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=1329437287.2869.22.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.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 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).