From: Paul Moore <pmoore@redhat.com>
To: netdev@vger.kernel.org
Cc: rdunlap@infradead.org
Subject: [PATCH] net: make CONFIG_NETLABEL explicitly dependent on CONFIG_INET
Date: Fri, 30 Nov 2012 10:35:19 -0500 [thread overview]
Message-ID: <20121130153518.16416.23470.stgit@sifl> (raw)
This should resolve an issue found during testing with random
configuration files.
net/built-in.o: In function `netlbl_cfg_cipsov4_add':
(.text+0x61757): undefined reference to `cipso_v4_doi_add'
net/built-in.o: In function `netlbl_cfg_cipsov4_del':
(.text+0x6177d): undefined reference to `cipso_v4_doi_remove'
[... and so on ...]
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Paul Moore <pmoore@redhat.com>
---
net/netlabel/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/netlabel/Kconfig b/net/netlabel/Kconfig
index 56958c8..f272826 100644
--- a/net/netlabel/Kconfig
+++ b/net/netlabel/Kconfig
@@ -4,7 +4,7 @@
config NETLABEL
bool "NetLabel subsystem support"
- depends on SECURITY
+ depends on SECURITY && INET
default n
---help---
NetLabel provides support for explicit network packet labeling
reply other threads:[~2012-11-30 15:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121130153518.16416.23470.stgit@sifl \
--to=pmoore@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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).