From: "J.A. Magallon" <jamagallon@able.es>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.20-pre1
Date: Wed, 7 Aug 2002 03:08:14 +0200 [thread overview]
Message-ID: <20020807010814.GA11603@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0208051938380.6811-100000@freak.distro.conectiva>; from marcelo@conectiva.com.br on Tue, Aug 06, 2002 at 00:40:56 +0200
On 2002.08.06 Marcelo Tosatti wrote:
>
>So here goes -pre1, with a big -ac and x86-64 merges, plus other smaller
>stuff.
>
Something is missing in the network merge:
werewolf:/usr/src/linux# grep -r netif_receive_skb *
drivers/net/tg3.c: netif_receive_skb(skb);
Binary file drivers/net/e1000/e1000_main.o matches
Binary file drivers/net/e1000/e1000.o matches
include/linux/if_vlan.h: //return (polling ? netif_receive_skb(skb) : netif_rx(skb));
So I had to:
--- linux/include/linux/if_vlan.h.orig 2002-08-07 02:57:36.000000000 +0200
+++ linux/include/linux/if_vlan.h 2002-08-07 02:58:07.000000000 +0200
@@ -183,7 +183,8 @@
break;
};
- return (polling ? netif_receive_skb(skb) : netif_rx(skb));
+ //return (polling ? netif_receive_skb(skb) : netif_rx(skb));
+ return netif_rx(skb);
}
static inline int vlan_hwaccel_rx(struct sk_buff *skb,
To make e1000 build. But tg3 uses n_r_skb directly, so it is not useful for
that.
--
J.A. Magallon \ Software is like sex: It's better when it's free
mailto:jamagallon@able.es \ -- Linus Torvalds, FSF T-shirt
Linux werewolf 2.4.19-jam0, Mandrake Linux 9.0 (Cooker) for i586
gcc (GCC) 3.2 (Mandrake Linux 9.0 3.2-0.2mdk)
next prev parent reply other threads:[~2002-08-07 1:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 22:40 Linux 2.4.20-pre1 Marcelo Tosatti
2002-08-06 0:20 ` Ben Greear
2002-08-06 11:32 ` Marcelo Tosatti
2002-08-06 12:26 ` David S. Miller
2002-08-06 16:45 ` Ben Greear
2002-08-06 17:12 ` NAPI (was Re: Linux 2.4.20-pre1) Jeff Garzik
2002-08-07 14:09 ` Marcus Sundberg
2002-08-06 14:58 ` Linux 2.4.20-pre1 Jason Lunz
2002-08-06 15:03 ` CaT
2002-08-06 21:05 ` Adrian Bunk
2002-08-07 11:09 ` David S. Miller
2002-08-07 0:21 ` J.A. Magallon
2002-08-07 1:08 ` J.A. Magallon [this message]
2002-08-07 1:56 ` Bryan Whitehead
2002-08-07 3:35 ` Tim Hockin
2002-08-11 8:57 ` Erik Andersen
2002-08-11 9:16 ` Christoph Hellwig
2002-08-11 9:40 ` Erik Andersen
2002-08-11 9:46 ` Erik Andersen
2002-08-11 19:46 ` Alan Cox
2002-08-11 18:49 ` Erik Andersen
2002-08-12 19:29 ` Paul P Komkoff Jr
2002-08-11 10:56 ` Erik Andersen
2002-08-11 21:22 ` [PATCH] radeonfb update vs 2.4.20-pre1 Erik Andersen
2002-08-12 10:18 ` Ani Joshi
2002-08-12 10:26 ` Erik Andersen
2002-08-17 19:51 ` Linux 2.4.20-pre1 Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2002-08-06 0:21 Jean Tourrilhes
2002-08-06 12:33 ` Marcelo Tosatti
2002-08-06 17:17 ` Jean Tourrilhes
2002-08-06 16:31 ` Marcelo Tosatti
2002-08-06 17:24 ` Jean Tourrilhes
2002-08-06 17:13 ` David S. Miller
2002-08-06 18:48 ` Alan Cox
2002-08-06 23:29 Alan Cox
[not found] <200208062329.g76NTqP30962@devserv.devel.redhat.com.suse.lists.linux.kernel>
2002-08-07 10:01 ` Andi Kleen
2002-08-07 11:50 ` Alan Cox
2002-08-11 21:12 Matt_Domsch
2002-08-15 17:28 Matt_Domsch
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=20020807010814.GA11603@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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