linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	shingo@flab.fujitsu.co.jp, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fmvj18x_cs: don't reference skb after passing it to netif_rx
Date: Mon, 26 Feb 2001 20:57:37 -0500	[thread overview]
Message-ID: <3A9B0991.F34AF284@mandrakesoft.com> (raw)
In-Reply-To: <20010226211403.N8692@conectiva.com.br>

[-- Attachment #1: Type: text/plain, Size: 201 bytes --]

Ditto...
-- 
Jeff Garzik       | "You see, in this world there's two kinds of
Building 1024     |  people, my friend: Those with loaded guns
MandrakeSoft      |  and those who dig. You dig."  --Blondie

[-- Attachment #2: fmv.patch --]
[-- Type: text/plain, Size: 602 bytes --]

Index: drivers/net/pcmcia/fmvj18x_cs.c
===================================================================
RCS file: /cvsroot/gkernel/linux_2_4/drivers/net/pcmcia/fmvj18x_cs.c,v
retrieving revision 1.1.1.14.2.2
diff -u -r1.1.1.14.2.2 fmvj18x_cs.c
--- drivers/net/pcmcia/fmvj18x_cs.c	2001/02/23 03:37:00	1.1.1.14.2.2
+++ drivers/net/pcmcia/fmvj18x_cs.c	2001/02/27 01:57:16
@@ -1080,8 +1080,9 @@
 #endif
 
 	    netif_rx(skb);
+	    dev->last_rx = jiffies;
 	    lp->stats.rx_packets++;
-	    lp->stats.rx_bytes += skb->len;
+	    lp->stats.rx_bytes += pkt_len;
 	}
 	if (--boguscount <= 0)
 	    break;

  parent reply	other threads:[~2001-02-27  1:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27  0:14 [PATCH] fmvj18x_cs: don't reference skb after passing it to netif_rx Arnaldo Carvalho de Melo
2001-02-27  0:41 ` [PATCH] tms380tr: update last_rx after netif_rx Arnaldo Carvalho de Melo
2001-02-27  1:57 ` Jeff Garzik [this message]
2001-02-27  0:25   ` [PATCH] fmvj18x_cs: don't reference skb after passing it to netif_rx Arnaldo Carvalho de Melo

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=3A9B0991.F34AF284@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=acme@conectiva.com.br \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shingo@flab.fujitsu.co.jp \
    /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).