> >
> > What is being done in the parent directory has a bug, you're right
> > that far, but this is the wrong fix. If you check the 0day failures,
> > it isn't because the InfiniBand core isn't enabled, it's because the
> > current menuconfig setup allows the IB core to be a module and the
> > staging drivers to be compiled into the kernel. That obviously is an
> > invalid condition and it applies to all of the drivers in staging right
> > now. The
> correct fix is to resolve that issue.
>
> That is our conclusion as well.
>
> But how do we do that globally in staging/rdma?
>
> The module setting of INFINIBAND does not seem to carry to the subdirs while
> the following does work.
>
> It seems like this is the easiest fix since this is a temp home for these
> drivers.
Ok looks like this will fix it... Still testing.
14:18:37 > git di
diff --git a/drivers/staging/rdma/Kconfig b/drivers/staging/rdma/Kconfig
index d7f62359d743..46ddc03c6839 100644
--- a/drivers/staging/rdma/Kconfig
+++ b/drivers/staging/rdma/Kconfig
@@ -1,10 +1,11 @@
menuconfig STAGING_RDMA
- bool "RDMA staging drivers"
+ tristate "RDMA staging drivers"
depends on INFINIBAND
depends on PCI || BROKEN
depends on HAS_IOMEM
depends on NET
depends on INET
+ depends on m
default n
---help---
This option allows you to select a number of RDMA drivers that
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
