linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Robert E Brose II <bob@kunk.jriver.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.9-benh0 problems and kudos
Date: Thu, 23 Aug 2001 20:00:20 -0500 (CDT)	[thread overview]
Message-ID: <20010824010020.2304.qmail@kunk.jriver.com> (raw)
In-Reply-To: <20010823130149.X14302@cpe-24-221-152-185.az.sprintbbd.net> "from Tom Rini at Aug 23, 2001 01:01:49 pm"


User Tom Rini says:
> > Did you mean sk_chk_filter?  The problem is that sk_{chk,run}_filter are
> > only exported on CONFIG_FILTER.  Congrats, you found a bug. :)  Go email
> > Dave S. Miller <davem@redhat.com> about this.  In the mean time, edit
> > net/netsyms.c, search for the symbols and remove the #ifdef CONFIG_FILTER/#endif
> > around them.  Re-run make dep and recompile.
>
> Er, wait a second...  drivers/net/pppoe.c doesn't call sk_run_filter...
>
> --
> Tom Rini (TR1265)
> http://gate.crashing.org/~trini/
>

UMMM, I don't see myself where it's getting it from however with a
clean compile I see the following...

# nm pppoe.o | grep sk_
         U sk_alloc_R5f9fe915
         U sk_free_R6807b2c7
         U sk_run_filter

Bob
--
Robert E. Brose II    N0QBJ
http://www.jriver.com/~bob/
bob@kunk.jriver.com

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-08-24  1:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-23 16:42 2.4.9-benh0 problems and kudos Robert E Brose II
2001-08-23 16:58 ` Tom Rini
2001-08-23 19:43   ` Robert E Brose II
2001-08-23 19:48     ` Tom Rini
2001-08-23 20:01       ` Tom Rini
2001-08-24  1:00         ` Robert E Brose II [this message]
2001-08-24  1:51           ` Tom Rini
2001-08-23 17:06 ` Olaf Hering
2001-08-23 19:29 ` Michel Lanners
2001-08-23 20:57   ` Robert E Brose II
2001-08-23 21:22   ` Robert E Brose II

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=20010824010020.2304.qmail@kunk.jriver.com \
    --to=bob@kunk.jriver.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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).