From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
ericvh@gmail.com, akpm <akpm@linux-foundation.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
v9fs-developer@lists.sourceforge.net,
netdev <netdev@vger.kernel.org>
Subject: [PATCH linux-next 3rd time] 9p: restrict RDMA usage
Date: Wed, 12 Nov 2008 13:05:17 -0800 [thread overview]
Message-ID: <20081112130517.73c3e13a.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20081112182818.6e259488.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
linux-next:
Make 9p's RDMA option depend on INET since it uses Infiniband rdma_*
functions and that code depends on INET. Otherwise 9p can try to
use symbols which don't exist.
ERROR: "rdma_destroy_id" [net/9p/9pnet_rdma.ko] undefined!
ERROR: "rdma_connect" [net/9p/9pnet_rdma.ko] undefined!
ERROR: "rdma_create_id" [net/9p/9pnet_rdma.ko] undefined!
ERROR: "rdma_create_qp" [net/9p/9pnet_rdma.ko] undefined!
ERROR: "rdma_resolve_route" [net/9p/9pnet_rdma.ko] undefined!
ERROR: "rdma_disconnect" [net/9p/9pnet_rdma.ko] undefined!
ERROR: "rdma_resolve_addr" [net/9p/9pnet_rdma.ko] undefined!
I used an if/endif block so that the menu items would remain
presented together.
Also correct an article adjective.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
net/9p/Kconfig | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
--- linux-next-20081103.orig/net/9p/Kconfig
+++ linux-next-20081103/net/9p/Kconfig
@@ -13,22 +13,24 @@ menuconfig NET_9P
If unsure, say N.
+if NET_9P
+
config NET_9P_VIRTIO
- depends on NET_9P && EXPERIMENTAL && VIRTIO
+ depends on EXPERIMENTAL && VIRTIO
tristate "9P Virtio Transport (Experimental)"
help
This builds support for a transports between
guest partitions and a host partition.
config NET_9P_RDMA
- depends on NET_9P && INFINIBAND && EXPERIMENTAL
+ depends on INET && INFINIBAND && EXPERIMENTAL
tristate "9P RDMA Transport (Experimental)"
help
- This builds support for a RDMA transport.
+ This builds support for an RDMA transport.
config NET_9P_DEBUG
bool "Debug information"
- depends on NET_9P
help
Say Y if you want the 9P subsystem to log debug information.
+endif
next prev parent reply other threads:[~2008-11-12 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 7:28 linux-next: Tree for November 12 Stephen Rothwell
2008-11-12 7:56 ` mac80211.h (was: Re: linux-next: Tree for November 12) Geert Uytterhoeven
2008-11-12 15:05 ` [PATCH] mac80211: add explicit padding in struct ieee80211_tx_info John W. Linville
2008-11-12 17:08 ` Johannes Berg
2008-11-12 9:11 ` linux-next: Tree for November 12 - lguest build failure Kamalesh Babulal
2008-11-12 10:40 ` Rusty Russell
2008-11-12 12:26 ` [Lguest] " Rusty Russell
2008-11-12 21:01 ` [PATCH linux-next] : Tree for November 12 (libcrc32c) Randy Dunlap
2008-11-13 14:09 ` Herbert Xu
2008-11-12 21:05 ` Randy Dunlap [this message]
2008-11-12 21:10 ` linux-next: Tree for November 12 (ipw2200 build error) Randy Dunlap
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=20081112130517.73c3e13a.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=v9fs-developer@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®