From: Bernhard Rosenkraenzer <bero@arklinux.org>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.6.18-rc2-mm1: unresolved symbol brnf_deferred_hooks in xt_physdev module
Date: Fri, 28 Jul 2006 13:38:21 +0200 [thread overview]
Message-ID: <200607281338.22053.bero@arklinux.org> (raw)
The (trivial) patch below fixes the unresolved symbol brnf_deferred_hooks in
the xt_physdev module in 2.6.18-rc2-mm1.
Signed-off-by: Bernhard Rosenkraenzer <bero@arklinux.org>
---
--- linux-2.6.17/net/netfilter/xt_physdev.c.ark 2006-07-28 13:34:31.000000000
+0200
+++ linux-2.6.17/net/netfilter/xt_physdev.c 2006-07-28 13:34:48.000000000
+0200
@@ -16,6 +16,8 @@
#define MATCH 1
#define NOMATCH 0
+extern int brnf_deferred_hooks;
+
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Bart De Schuymer <bdschuym@pandora.be>");
MODULE_DESCRIPTION("iptables bridge physical device match module");
next reply other threads:[~2006-07-28 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 11:38 Bernhard Rosenkraenzer [this message]
2006-07-29 5:00 ` [PATCH] 2.6.18-rc2-mm1: unresolved symbol brnf_deferred_hooks in xt_physdev module Andrew Morton
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=200607281338.22053.bero@arklinux.org \
--to=bero@arklinux.org \
--cc=akpm@osdl.org \
--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).