From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
Neil Brown <neilb@suse.de>, Roland Dreier <rolandd@cisco.com>,
Dave Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: [PATCH] sunrpc: fix rdma dependencies
Date: Tue, 03 Feb 2009 14:13:15 -0800 [thread overview]
Message-ID: <4988C17B.1030902@oracle.com> (raw)
In-Reply-To: <200902030112.n131CNiq010549@imap1.linux-foundation.org>
Andrew Morton wrote:
> This patch was dropped because other changes were merged, which wrecked this patch.
The kconfig just moved from one file to another one. The problem is still there.
---
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix sunrpc/rdma build dependencies.
Survives 12 build combinations of INET, IPV6, SUNRPC,
INFINIBAND, and INFINIBAND_ADDR_TRANS.
ERROR: "rdma_destroy_id" [net/sunrpc/xprtrdma/xprtrdma.ko] undefined!
ERROR: "rdma_connect" [net/sunrpc/xprtrdma/xprtrdma.ko] undefined!
ERROR: "rdma_destroy_qp" [net/sunrpc/xprtrdma/xprtrdma.ko] undefined!
ERROR: "rdma_create_id" [net/sunrpc/xprtrdma/xprtrdma.ko] undefined!
ERROR: "rdma_create_qp" [net/sunrpc/xprtrdma/xprtrdma.ko] undefined!
ERROR: "rdma_resolve_route" [net/sunrpc/xprtrdma/xprtrdma.ko] undefined!
ERROR: "rdma_disconnect" [net/sunrpc/xprtrdma/xprtrdma.ko] undefined!
ERROR: "rdma_resolve_addr" [net/sunrpc/xprtrdma/xprtrdma.ko] undefined!
ERROR: "rdma_accept" [net/sunrpc/xprtrdma/svcrdma.ko] undefined!
ERROR: "rdma_destroy_id" [net/sunrpc/xprtrdma/svcrdma.ko] undefined!
ERROR: "rdma_listen" [net/sunrpc/xprtrdma/svcrdma.ko] undefined!
ERROR: "rdma_create_id" [net/sunrpc/xprtrdma/svcrdma.ko] undefined!
ERROR: "rdma_create_qp" [net/sunrpc/xprtrdma/svcrdma.ko] undefined!
ERROR: "rdma_bind_addr" [net/sunrpc/xprtrdma/svcrdma.ko] undefined!
ERROR: "rdma_disconnect" [net/sunrpc/xprtrdma/svcrdma.ko] undefined!
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
cc: J. Bruce Fields <bfields@fieldses.org>
cc: Neil Brown <neilb@suse.de>
cc: Roland Dreier <rolandd@cisco.com>
cc: Dave Miller <davem@davemloft.net>
---
net/sunrpc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- mmotm-2009-0202-1712.orig/net/sunrpc/Kconfig
+++ mmotm-2009-0202-1712/net/sunrpc/Kconfig
@@ -6,7 +6,7 @@ config SUNRPC_GSS
config SUNRPC_XPRT_RDMA
tristate
- depends on SUNRPC && INFINIBAND && EXPERIMENTAL
+ depends on SUNRPC && INFINIBAND && INFINIBAND_ADDR_TRANS && EXPERIMENTAL
default SUNRPC && INFINIBAND
help
This option allows the NFS client and server to support
next prev parent reply other threads:[~2009-02-03 22:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 1:12 mmotm 2009-02-02-17-12 uploaded akpm
2009-02-03 18:58 ` mmotm 2009-02-02-17-12 uploaded (x86/nopmd etc.) Randy Dunlap
2009-02-03 19:18 ` Ingo Molnar
2009-02-03 20:17 ` Andrew Morton
2009-02-03 21:25 ` Ingo Molnar
2009-02-03 21:41 ` Andrew Morton
2009-02-04 20:08 ` Ingo Molnar
2009-02-04 21:25 ` Andrew Morton
2009-02-04 21:29 ` Ingo Molnar
2009-02-04 21:32 ` Andrea Righi
2009-02-03 22:37 ` Jeremy Fitzhardinge
2009-02-04 19:56 ` Ingo Molnar
2009-02-03 22:13 ` Randy Dunlap [this message]
2009-02-03 23:20 ` [PATCH] sunrpc: fix rdma dependencies David Miller
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=4988C17B.1030902@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=rolandd@cisco.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.