From: Jason Gunthorpe <jgg@ziepe.ca>
To: Steve Wise <swise@opengridcomputing.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Steve Wise <swise@chelsio.com>,
Doug Ledford <dledford@redhat.com>,
Yuval Shaia <yuval.shaia@oracle.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iw_cxgb4: add INFINIBAND_ADDR_TRANS dependency
Date: Wed, 30 May 2018 16:25:20 -0600 [thread overview]
Message-ID: <20180530222520.GJ30754@ziepe.ca> (raw)
In-Reply-To: <0be4e0fb-8d8e-b337-fc8d-550c90829d8c@opengridcomputing.com>
On Wed, May 30, 2018 at 05:10:35PM -0500, Steve Wise wrote:
>
>
> On 5/30/2018 5:04 PM, Jason Gunthorpe wrote:
> > On Wed, May 30, 2018 at 11:58:18PM +0200, Arnd Bergmann wrote:
> >> The newly added fill_res_ep_entry function fails to link if
> >> CONFIG_INFINIBAND_ADDR_TRANS is not set:
> >>
> >> drivers/infiniband/hw/cxgb4/restrack.o: In function `fill_res_ep_entry':
> >> restrack.c:(.text+0x3cc): undefined reference to `rdma_res_to_id'
> >> restrack.c:(.text+0x3d0): undefined reference to `rdma_iw_cm_id'
> >>
> >> This adds a Kconfig dependency for the driver.
> >>
> >> Fixes: 116aeb887371 ("iw_cxgb4: provide detailed provider-specific CM_ID information")
> >> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >> drivers/infiniband/hw/cxgb4/Kconfig | 1 +
> >> 1 file changed, 1 insertion(+)
> > Oh, I think we need to solve this with maybe a header fill null stub
> > instead..
> >
> > We don't want to disable drivers just because a user interface is
> > disabled.
> >
>
> Why does CONFIG_INFINIBAND_ADDR_TRANS disable building rdma_cm.ko? That
> is not correct.
That seems like a reasonable thing to do..
But why does it break the compile? Those functions are in cma.c...
Jason
next prev parent reply other threads:[~2018-05-30 22:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 21:58 [PATCH] iw_cxgb4: add INFINIBAND_ADDR_TRANS dependency Arnd Bergmann
2018-05-30 22:04 ` Jason Gunthorpe
2018-05-30 22:10 ` Steve Wise
2018-05-30 22:25 ` Jason Gunthorpe [this message]
2018-05-30 22:29 ` Steve Wise
2018-05-30 22:40 ` Arnd Bergmann
2018-05-30 23:01 ` Jason Gunthorpe
2018-05-31 4:03 ` Greg Thelen
2018-05-31 18:40 ` Doug Ledford
2018-06-04 23:07 ` Jason Gunthorpe
2018-06-07 8:10 ` Greg Thelen
2018-06-07 18:00 ` Jason Gunthorpe
2018-06-04 15:36 ` Jason Gunthorpe
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=20180530222520.GJ30754@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=arnd@arndb.de \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=swise@chelsio.com \
--cc=swise@opengridcomputing.com \
--cc=yuval.shaia@oracle.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