netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: netdev@oss.sgi.com
Subject: Re: [PATCH]  e100: Enable receiving bogus packets, and transmitting bad/custom CRC
Date: Tue, 25 Nov 2003 15:42:49 +0100	[thread overview]
Message-ID: <20031125154249.B1107@sygehus.dk> (raw)
In-Reply-To: <20031124173330.096c0751.davem@redhat.com>; from davem@redhat.com on Mon, Nov 24, 2003 at 05:33:30PM -0800

On Mon, Nov 24, 2003 at 05:33:30PM -0800, David S. Miller wrote:
> On Mon, 24 Nov 2003 15:48:25 -0800
> Ben Greear <greearb@candelatech.com> wrote:
> 
> > Btw, it's impossible (afaik) to see the CRC errors generically w/out
> > accessing netlink (which I assume works, but have never actually tried), ie

> The netlink thing does work, trust me :)
> You could argue that 'ip -s link' should print this out, and I'd
> agree with you on that.

Give it another -s, i.e. 'ip -s -s link', and it does. :-)

-- 
Regards,
Rask Ingemann Lambertsen

  parent reply	other threads:[~2003-11-25 14:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 23:24 [PATCH] e100: Enable receiving bogus packets, and transmitting bad/custom CRC Ben Greear
2003-11-24 23:29 ` David S. Miller
2003-11-24 23:48   ` Ben Greear
2003-11-25  1:33     ` David S. Miller
2003-11-25  7:53       ` [PATCH 0/3] e100: Enable receiving bogus packets and saving FCS Ben Greear
2003-11-25 14:42       ` Rask Ingemann Lambertsen [this message]
2003-11-25 14:45         ` [PATCH] e100: Enable receiving bogus packets, and transmitting bad/custom CRC David S. Miller
2003-11-25 14:56     ` Rask Ingemann Lambertsen
2003-12-13 19:00 ` Rask Ingemann Lambertsen
2003-12-13 19:12   ` Ben Greear

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=20031125154249.B1107@sygehus.dk \
    --to=rask@sygehus.dk \
    --cc=netdev@oss.sgi.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).