From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Mike Marciniszyn <infinipath@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
devel@driverdev.osuosl.org, Jim Davis <jim.epost@gmail.com>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: [PATCH] staging: ipath: fix build failure
Date: Tue, 1 Sep 2015 18:31:38 +0530 [thread overview]
Message-ID: <1441112498-22057-1-git-send-email-sudipm.mukherjee@gmail.com> (raw)
building of ipath depends on infiniband. And if ipath is selected and
infiniband is not then build fails with:
ERROR: "ib_alloc_device" [drivers/staging/ipath/ib_ipath.ko] undefined!
ERROR: "ib_dealloc_device" [drivers/staging/ipath/ib_ipath.ko] undefined!
ERROR: "ib_dispatch_event" [drivers/staging/ipath/ib_ipath.ko] undefined!
ERROR: "ib_register_device" [drivers/staging/ipath/ib_ipath.ko] undefined!
ERROR: "ib_unregister_device" [drivers/staging/ipath/ib_ipath.ko] undefined!
ERROR: "ib_modify_qp_is_ok" [drivers/staging/ipath/ib_ipath.ko] undefined!
ERROR: "ib_wq" [drivers/staging/ipath/ib_ipath.ko] undefined!
Config at: https://lkml.org/lkml/2015/8/31/328
Reported-by: Jim Davis <jim.epost@gmail.com>
Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
---
drivers/staging/ipath/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/ipath/Kconfig b/drivers/staging/ipath/Kconfig
index 041ce06..1edc21b 100644
--- a/drivers/staging/ipath/Kconfig
+++ b/drivers/staging/ipath/Kconfig
@@ -1,6 +1,7 @@
config INFINIBAND_IPATH
tristate "QLogic HTX HCA support"
depends on 64BIT && NET && HT_IRQ
+ depends on INFINIBAND
---help---
This is a driver for the deprecated QLogic Hyper-Transport
IB host channel adapter (model QHT7140),
--
1.9.1
next reply other threads:[~2015-09-01 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 13:01 Sudip Mukherjee [this message]
2015-09-01 14:52 ` Doug Ledford
2015-09-01 16:54 ` Jim Davis
2015-09-01 16:59 ` Doug Ledford
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=1441112498-22057-1-git-send-email-sudipm.mukherjee@gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=infinipath@intel.com \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.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
all inboxes | Powered by JetHome®