public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Sjur Brendeland <sjur.brandeland@stericsson.com>
Subject: [PATCH -next] xshm: fix build errors, depends on NET
Date: Fri, 09 Dec 2011 14:21:50 -0800	[thread overview]
Message-ID: <4EE289FE.90006@xenotime.net> (raw)
In-Reply-To: <20111209163247.1de15dcb5b735ca5e1ad030b@canb.auug.org.au>

From: Randy Dunlap <rdunlap@xenotime.net>

Fix build errors in xshm.  xshm uses netlink, so it
should depend on NET.

ERROR: "genl_unregister_family" [drivers/xshm/xshm.ko] undefined!
ERROR: "netlink_unicast" [drivers/xshm/xshm.ko] undefined!
ERROR: "genl_register_family_with_ops" [drivers/xshm/xshm.ko] undefined!
ERROR: "init_net" [drivers/xshm/xshm.ko] undefined!
ERROR: "__alloc_skb" [drivers/xshm/xshm.ko] undefined!
ERROR: "kfree_skb" [drivers/xshm/xshm.ko] undefined!
ERROR: "skb_put" [drivers/xshm/xshm.ko] undefined!

Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
Cc: Sjur Brendeland <sjur.brandeland@stericsson.com>
---
 drivers/xshm/Kconfig |    1 +
 1 file changed, 1 insertion(+)

--- linux-next-20111209.orig/drivers/xshm/Kconfig
+++ linux-next-20111209/drivers/xshm/Kconfig
@@ -5,6 +5,7 @@ config XSHM
 
 config XSHM_CHR
 	tristate "Character device for External Shared Memory (XSHM)"
+	depends on NET
 	select XSHM
 	default n
 	---help---

  parent reply	other threads:[~2011-12-09 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09  5:32 linux-next: Tree for Dec 9 Stephen Rothwell
2011-12-09 18:51 ` linux-next: Tree for Dec 9 (ibmphp) Randy Dunlap
2011-12-12 17:20   ` Randy Dunlap
2011-12-14  0:41     ` Bjorn Helgaas
2011-12-14 16:30       ` Jesse Barnes
2011-12-16 18:42       ` Randy Dunlap
2011-12-09 22:21 ` Randy Dunlap [this message]
2011-12-12  7:52   ` [PATCH -next] xshm: fix build errors, depends on NET Sjur BRENDELAND

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=4EE289FE.90006@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sjur.brandeland@stericsson.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox