All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Lehtiniemi <rayl@mail.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: jeff@garzik.org, netdev@vger.kernel.org,
	Herbert Valerio Riedel <hvr@gnu.org>
Subject: Re: [PATCH 3/3] ep93xx_eth: don't report RX FIFO overrun errors
Date: Sun, 29 Oct 2006 11:41:00 -0700	[thread overview]
Message-ID: <200610291141.00866.rayl@mail.com> (raw)
In-Reply-To: <20061029182253.GE7055@xi.wantstofly.org>

On Sunday 29 October 2006 11:22, Lennert Buytenhek wrote:

> > Also, is it possible for any other error bits to be set at the same
> > time as OE?  such bits would not be printed to the log in this case.
>
> Not sure, but arguably, this wouldn't be very interesting.  Actually,
> now I'm wondering whether we should just remove the printk altogether.

i don't see why we need a printk... the error counters _should_ be sufficient.

ray

      reply	other threads:[~2006-10-29 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29 13:06 [PATCH 3/3] ep93xx_eth: don't report RX FIFO overrun errors Lennert Buytenhek
2006-10-29 18:15 ` Ray Lehtiniemi
2006-10-29 18:22   ` Lennert Buytenhek
2006-10-29 18:41     ` Ray Lehtiniemi [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=200610291141.00866.rayl@mail.com \
    --to=rayl@mail.com \
    --cc=buytenh@wantstofly.org \
    --cc=hvr@gnu.org \
    --cc=jeff@garzik.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.