From: Christian <evil@g-house.de>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: 2.6.15-rc1: NET_CLS_U32 not working?
Date: Thu, 17 Nov 2005 01:06:38 +0100 [thread overview]
Message-ID: <437BC98E.9020002@g-house.de> (raw)
In-Reply-To: <20051116235813.GS5735@stusta.de>
Adrian Bunk schrieb:
>
> I'm assuming you are trying to insert the new module in your old kernel?
yes, i tried to "modprobe" the compiled cls_u32 module. but the "make
modules" errors are there anyway. i tried to compile a fresh 2.6.15-rc1
on a different machine (where i can't do "modprobe") and the errors were
there too: http://nerdbynature.de/bits/sheep/2.6.15-rc1/make-modules.log
> This is one of the unfortunate but hardly avoidable cases where adding a
> module requires installing a new kernel.
despite of the errors on "make modules" i'll reboot with the "new"
kernel asap.
> BTW: Please Cc netdev@vger.kernel.org on networking issues.
ok, will do that.
thank you,
Christian.
--
BOFH excuse #442:
Trojan horse ran out of hay
next prev parent reply other threads:[~2005-11-17 0:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <437BBC59.70301@g-house.de>
2005-11-16 23:58 ` 2.6.15-rc1: NET_CLS_U32 not working? Adrian Bunk
2005-11-17 0:06 ` Christian [this message]
2005-11-17 15:57 ` Christian
2005-11-21 15:59 ` [2.6 patch] do not select NET_CLS Adrian Bunk
2005-11-21 16:16 ` Patrick McHardy
2005-11-22 22:37 ` David S. Miller
2005-11-22 22:49 ` Sam Ravnborg
2005-11-22 23:00 ` David S. Miller
2005-11-23 5:57 ` Sam Ravnborg
2005-11-24 2:13 ` Randy.Dunlap
2005-11-24 5:40 ` Sam Ravnborg
2005-11-22 23:12 ` Adrian Bunk
2005-11-23 10:27 ` Thomas Graf
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=437BC98E.9020002@g-house.de \
--to=evil@g-house.de \
--cc=linux-kernel@vger.kernel.org \
--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).