All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: bridge@lists.linux-foundation.org, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: [Bridge] [PATCH -next] bridge: depends on INET
Date: Tue, 02 Mar 2010 09:08:23 -0800	[thread overview]
Message-ID: <4B8D4607.8070603@xenotime.net> (raw)
In-Reply-To: <20100302180915.1388d3f3.sfr@canb.auug.org.au>

From: Randy Dunlap <randy.dunlap@oracle.com>

br_multicast calls ip_send_check(), so it should depend on INET.

built-in:
br_multicast.c:(.text+0x88cf4): undefined reference to `ip_send_check'

or modular:
ERROR: "ip_send_check" [net/bridge/bridge.ko] undefined!

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: bridge@lists.linux-foundation.org
---
 net/bridge/Kconfig |    1 +
 1 file changed, 1 insertion(+)

--- linux-next-20100302.orig/net/bridge/Kconfig
+++ linux-next-20100302/net/bridge/Kconfig
@@ -35,6 +35,7 @@ config BRIDGE
 config BRIDGE_IGMP_SNOOPING
 	bool "IGMP snooping"
 	depends on BRIDGE
+	depends on INET
 	default y
 	---help---
 	  If you say Y here, then the Ethernet bridge will be able selectively

WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	bridge@lists.linux-foundation.org
Subject: [PATCH -next] bridge: depends on INET
Date: Tue, 02 Mar 2010 09:08:23 -0800	[thread overview]
Message-ID: <4B8D4607.8070603@xenotime.net> (raw)
In-Reply-To: <20100302180915.1388d3f3.sfr@canb.auug.org.au>

From: Randy Dunlap <randy.dunlap@oracle.com>

br_multicast calls ip_send_check(), so it should depend on INET.

built-in:
br_multicast.c:(.text+0x88cf4): undefined reference to `ip_send_check'

or modular:
ERROR: "ip_send_check" [net/bridge/bridge.ko] undefined!

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: bridge@lists.linux-foundation.org
---
 net/bridge/Kconfig |    1 +
 1 file changed, 1 insertion(+)

--- linux-next-20100302.orig/net/bridge/Kconfig
+++ linux-next-20100302/net/bridge/Kconfig
@@ -35,6 +35,7 @@ config BRIDGE
 config BRIDGE_IGMP_SNOOPING
 	bool "IGMP snooping"
 	depends on BRIDGE
+	depends on INET
 	default y
 	---help---
 	  If you say Y here, then the Ethernet bridge will be able selectively

  reply	other threads:[~2010-03-02 17:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02  7:09 linux-next: Tree for March 2 Stephen Rothwell
2010-03-02 17:08 ` Randy Dunlap [this message]
2010-03-02 17:08   ` [PATCH -next] bridge: depends on INET Randy Dunlap
2010-03-03  9:23   ` [Bridge] " David Miller
2010-03-03  9:23     ` David Miller
2010-03-04  3:18     ` [Bridge] " Ingo Molnar
2010-03-04  3:18       ` Ingo Molnar
2010-03-04  4:00       ` [Bridge] " Randy Dunlap
2010-03-04  4:00         ` Randy Dunlap
2010-03-04  8:42       ` [Bridge] " David Miller
2010-03-04  8:42         ` David Miller
2010-03-02 17:12 ` linux-next: Tree for March 2 (watchdog) Randy Dunlap
2010-03-02 20:46   ` Wim Van Sebroeck

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=4B8D4607.8070603@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=bridge@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.