netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: David.Woodhouse@intel.com, romieu@fr.zoreil.com, netdev@vger.kernel.org
Subject: Re: [PATCH net] 8139cp: reset BQL when ring tx ring cleared
Date: Sat, 11 May 2013 18:21:25 -0700 (PDT)	[thread overview]
Message-ID: <20130511.182125.896338102769943216.davem@davemloft.net> (raw)
In-Reply-To: <20130511170923.52673453@nehalam.linuxnetplumber.net>

From: Stephen Hemminger <stephen@networkplumber.org>
Date: Sat, 11 May 2013 17:09:23 -0700

> While looking for other problem found this potential issue.
> When the transmit ring is cleaned out, the Byte Queue Limit values
> need to be reset.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>

You neither compiled, nor tested this.

  reply	other threads:[~2013-05-12  1:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-12  0:09 [PATCH net] 8139cp: reset BQL when ring tx ring cleared Stephen Hemminger
2013-05-12  1:21 ` David Miller [this message]
2013-05-12  2:30   ` Stephen Hemminger

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=20130511.182125.896338102769943216.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=David.Woodhouse@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=stephen@networkplumber.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).