From: Stephan von Krawczynski <skraw@ithnet.com>
To: johnpol@2ka.mipt.ru
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18-pre7: compile error
Date: Thu, 24 Jan 2002 21:21:46 +0100 [thread overview]
Message-ID: <20020124212146.0023e490.skraw@ithnet.com> (raw)
In-Reply-To: <20020124030106.2ac290dd.johnpol@2ka.mipt.ru>
In-Reply-To: <Pine.LNX.4.21.0201231953410.4134-100000@freak.distro.conectiva> <200201232346.AAA12999@webserver.ithnet.com> <20020124030106.2ac290dd.johnpol@2ka.mipt.ru>
On Thu, 24 Jan 2002 03:01:06 +0300
Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
> On Thu, 24 Jan 2002 00:46:45 +0100
> Stephan von Krawczynski <skraw@ithnet.com> wrote:
>
> > "I am sorry, Dave. I'm afraid I can't do that":
>
> > ipfwadm_core.o ipfwadm_core.c
> > ipfwadm_core.c: In function `free_fw_chain':
> > ipfwadm_core.c:691: called object is not a function
> > ipfwadm_core.c: In function `insert_in_chain':
> > ipfwadm_core.c:735: called object is not a function
> > ipfwadm_core.c: In function `append_to_chain':
> > ipfwadm_core.c:786: called object is not a function
> > ipfwadm_core.c: In function `del_from_chain':
> > ipfwadm_core.c:861: called object is not a function
>
> I hope this patch will help you:
Yes, in principal, but unfortunately the white spaces were tilted
in your patch, so here is a corrected version for inclusion.
Thanks Evgeniy.
--- linux/net/ipv4/netfilter/ipfwadm_core.c~ Thu Jan 24 21:16:02 2002
+++ linux/net/ipv4/netfilter/ipfwadm_core.c Thu Jan 24 21:16:38 2002
@@ -688,7 +688,7 @@
ftmp = *chainptr;
*chainptr = ftmp->fw_next;
kfree(ftmp);
- MOD_DEC_USE_COUNT();
+ MOD_DEC_USE_COUNT;
}
restore_flags(flags);
}
@@ -732,7 +732,7 @@
ftmp->fw_next = *chainptr;
*chainptr=ftmp;
restore_flags(flags);
- MOD_INC_USE_COUNT();
+ MOD_INC_USE_COUNT;
return(0);
}
@@ -783,7 +783,7 @@
else
*chainptr=ftmp;
restore_flags(flags);
- MOD_INC_USE_COUNT();
+ MOD_INC_USE_COUNT;
return(0);
}
@@ -858,7 +858,7 @@
}
restore_flags(flags);
if (was_found) {
- MOD_DEC_USE_COUNT();
+ MOD_DEC_USE_COUNT;
return 0;
} else
return(EINVAL);
next prev parent reply other threads:[~2002-01-24 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 21:55 Linux 2.4.18-pre7 Marcelo Tosatti
2002-01-23 23:19 ` CaT
2002-01-25 7:34 ` netfilter changes in 2.4.18-pre7 (was Re: Linux 2.4.18-pre7) Harald Welte
2002-01-23 23:46 ` Linux 2.4.18-pre7: compile error Stephan von Krawczynski
2002-01-24 0:01 ` Evgeniy Polyakov
2002-01-24 20:21 ` Stephan von Krawczynski [this message]
2002-01-24 0:41 ` Linux 2.4.18-pre7 Keith Owens
2002-01-24 3:14 ` Stephen Rothwell
2002-01-24 8:56 ` Philipp Matthias Hahn
2002-01-25 7:36 ` Harald Welte
2002-01-24 21:00 ` 2.4.18-pre7 cant find scsi disks George Bonser
2002-01-24 22:49 ` Linux 2.4.18-pre7 Rasmus Andersen
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=20020124212146.0023e490.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=johnpol@2ka.mipt.ru \
--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