All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Gerrit Huizenga <gh@us.ibm.com>,
	Chandra Seetharaman <sekharan@us.ibm.com>,
	Hubertus Franke <frankeh@us.ibm.com>,
	Shailabh Nagar <nagar@us.ibm.com>,
	Vivek Kashyap <vivk@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: [-mm patch] CKRM_TYPE_SOCKETCLASS must depend on INET
Date: Sun, 17 Jul 2005 22:33:54 +0200	[thread overview]
Message-ID: <20050717203354.GC3753@stusta.de> (raw)

CKRM_TYPE_SOCKETCLASS=y, NET=n, INET=n results in the following link 
error:

<--  snip  -->

...
  LD      .tmp_vmlinux1
kernel/built-in.o: In function `cb_sockclass_listen_stop':
ckrm_sockc.c:(.text+0x27e2b): undefined reference to `sk_free'
kernel/built-in.o: In function `ckrm_sock_forced_reclassify_ns':
ckrm_sockc.c:(.text+0x280d5): undefined reference to 
`tcp_v4_lookup_listener'
ckrm_sockc.c:(.text+0x280e4): undefined reference to `lock_sock'
ckrm_sockc.c:(.text+0x28134): undefined reference to `release_sock'
ckrm_sockc.c:(.text+0x28154): undefined reference to `sk_free'
kernel/built-in.o: In function `ckrm_sock_reclassify_class':
ckrm_sockc.c:(.text+0x2851e): undefined reference to `lock_sock'
ckrm_sockc.c:(.text+0x2853b): undefined reference to `release_sock'
make: *** [.tmp_vmlinux1] Error 1

<--  snip  -->


Signed-off-by: Adrian Bunk <bunk@stusta.de>

--- linux-2.6.13-rc3-mm1-full/init/Kconfig.old	2005-07-17 21:45:25.000000000 +0200
+++ linux-2.6.13-rc3-mm1-full/init/Kconfig	2005-07-17 21:46:03.000000000 +0200
@@ -184,7 +184,7 @@
 
 config CKRM_TYPE_SOCKETCLASS
 	bool "Class Manager for socket groups"
-	depends on CKRM && RCFS_FS
+	depends on INET && CKRM && RCFS_FS
 	default y
 	help
 	  SOCKET provides the extensions for CKRM to track per socket


                 reply	other threads:[~2005-07-17 20:34 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=20050717203354.GC3753@stusta.de \
    --to=bunk@stusta.de \
    --cc=frankeh@us.ibm.com \
    --cc=gh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nagar@us.ibm.com \
    --cc=sekharan@us.ibm.com \
    --cc=vivk@us.ibm.com \
    /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.