netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Dillow <dave@thedillows.org>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 18/21] net: typhoon: use common rx_copybreak handling
Date: Sat, 09 Jul 2011 13:46:54 -0400	[thread overview]
Message-ID: <1310233614.12566.1.camel@obelisk.thedillows.org> (raw)
In-Reply-To: <86c335595654802d096c5c6c79f5d3fb71d4bd22.1310229312.git.mirq-linux@rere.qmqm.pl>

On Sat, 2011-07-09 at 19:17 +0200, Michał Mirosław wrote:
> v2: fix inverted test on skb refill/reuse
> 
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> ---
>  drivers/net/typhoon.c |   26 +++++++-------------------

Looks good,

Acked-by: David Dillow <dave@thedillows.org>


  reply	other threads:[~2011-07-09 17:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09 17:17 [PATCH 00/21] clean up rx_copybreak handling [split version] Michał Mirosław
2011-07-09 17:17 ` [PATCH 08/21] net: natsemi: use common rx_copybreak handling Michał Mirosław
2011-07-09 17:17 ` [PATCH 06/21] net: ibmveth: make rx_copybreak threshold consistent with other drivers Michał Mirosław
2011-07-09 17:17 ` [PATCH 04/21] net: fealnx: use common rx_copybreak handling Michał Mirosław
2011-07-09 17:17 ` [PATCH 02/21] net: 3c59x: " Michał Mirosław
2011-07-09 22:22   ` Francois Romieu
2011-07-09 23:23     ` Michał Mirosław
2011-07-10  7:24       ` Francois Romieu
2011-07-09 17:17 ` [PATCH 05/21] net: hamachi: " Michał Mirosław
2011-07-09 17:17 ` [PATCH 07/21] net: lib82596: use common rx_copybreak handling [strict refill!] Michał Mirosław
2011-07-09 22:25   ` Francois Romieu
2011-07-09 17:17 ` [PATCH 03/21] net: epic100: use common rx_copybreak handling Michał Mirosław
2011-07-09 17:17 ` [PATCH 01/21] net: wrap common patterns of rx handler code Michał Mirosław
2011-07-09 17:17 ` [PATCH 10/21] net: sgiseeq: use common rx_copybreak handling [strict refill!] Michał Mirosław
2011-07-09 17:17 ` [PATCH 12/21] net: starfire: use common rx_copybreak handling Michał Mirosław
2011-07-09 17:17 ` [PATCH 13/21] net: sundance: " Michał Mirosław
2011-07-09 17:17 ` [PATCH 11/21] net: sis190: " Michał Mirosław
2011-07-09 17:17 ` [PATCH 09/21] net: pcnet32: use common rx_copybreak handling [strict refill!] Michał Mirosław
2011-07-09 22:28   ` Francois Romieu
2011-07-09 17:17 ` [PATCH 14/21] net: tg3: mark bad rx handler behaviour " Michał Mirosław
2011-07-09 17:17 ` [PATCH 21/21] net: yellowfin: use common rx_copybreak handling Michał Mirosław
2011-07-09 17:17 ` [PATCH 16/21] net: tulip/interrupt.c: " Michał Mirosław
2011-07-09 17:17 ` [PATCH 15/21] net: tulip/de2104x: use common rx_copybreak handling [strict refill!] Michał Mirosław
2011-07-09 22:31   ` Francois Romieu
2011-07-09 17:17 ` [PATCH 17/21] net: tulip/winbond-840: use common rx_copybreak handling Michał Mirosław
2011-07-09 17:17 ` [PATCH 20/21] net: via-velocity: " Michał Mirosław
2011-07-09 22:19   ` Francois Romieu
2011-07-09 17:17 ` [PATCH 18/21] net: typhoon: " Michał Mirosław
2011-07-09 17:46   ` David Dillow [this message]
2011-07-09 17:17 ` [PATCH 19/21] net: via-rhine: " Michał Mirosław
2011-07-09 18:20 ` [PATCH 00/21] clean up rx_copybreak handling [split version] Joe Perches
2011-07-10 11:28   ` Michał Mirosław
2011-07-10 11:52     ` Michał Mirosław
2011-07-10 15:11       ` Joe Perches

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=1310233614.12566.1.camel@obelisk.thedillows.org \
    --to=dave@thedillows.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --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).