From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Jochen Friedrich <jochen@scram.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.3.39 LLC on Alpha broken?
Date: Mon, 30 Sep 2002 15:07:32 -0300 [thread overview]
Message-ID: <20020930180732.GG13478@conectiva.com.br> (raw)
In-Reply-To: <Pine.LNX.4.44.0209301956320.1163-100000@alpha.bocc.de>
Em Mon, Sep 30, 2002 at 07:58:43PM +0200, Jochen Friedrich escreveu:
> Hi,
>
> > I'll try to reboot the remaining mess and report how far it gets...
>
> It looks like LLC is the culprit for me:
Yes, it is, this is fixed in Linus bk tree, snap_init has to be called after
llc_init, this is the patch:
diff -Nru a/net/Makefile b/net/Makefile
--- a/net/Makefile Wed Sep 18 22:54:43 2002
+++ b/net/Makefile Mon Sep 30 00:11:16 2002
@@ -9,6 +9,8 @@
obj-y := socket.o core/
+# LLC has to be linked before the files in net/802/
+obj-$(CONFIG_LLC) += llc/
obj-$(CONFIG_NET) += ethernet/ 802/ sched/ netlink/
obj-$(CONFIG_INET) += ipv4/
obj-$(CONFIG_UNIX) += unix/
@@ -31,7 +33,6 @@
obj-$(CONFIG_DECNET) += decnet/
obj-$(CONFIG_ECONET) += econet/
obj-$(CONFIG_VLAN_8021Q) += 8021q/
-obj-$(CONFIG_LLC) += llc/
obj-$(CONFIG_IP_SCTP) += sctp/
ifeq ($(CONFIG_NET),y)
next prev parent reply other threads:[~2002-09-30 18:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 7:46 2.3.39 compile errors on Alpha Jochen Friedrich
2002-09-30 7:59 ` Jochen Friedrich
2002-09-30 11:08 ` Adrian Bunk
2002-09-30 12:35 ` Alan Cox
2002-09-30 12:25 ` David S. Miller
2002-09-30 13:15 ` Alan Cox
2002-09-30 13:20 ` 2.5.39 XConfig Processor Detection Adam Voigt
2002-09-30 13:30 ` Dave Jones
2002-09-30 13:48 ` Adam Voigt
2002-09-30 20:39 ` 2.3.39 compile errors on Alpha David S. Miller
2002-09-30 17:58 ` 2.3.39 LLC on Alpha broken? Jochen Friedrich
2002-09-30 18:07 ` Arnaldo Carvalho de Melo [this message]
2002-09-30 8:04 ` Jochen Friedrich
2002-09-30 21:04 ` Jochen Friedrich
2002-10-01 14:46 ` Ivan Kokshaysky
2002-10-01 16:05 ` Falk Hueffner
2002-09-30 20:59 ` David S. Miller
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=20020930180732.GG13478@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=jochen@scram.de \
--cc=linux-kernel@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).