From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Or Gerlitz <or.gerlitz@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org,
target-devel <target-devel@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 17 (infiniband/rdma)
Date: Wed, 17 Apr 2013 11:44:54 -0700 [thread overview]
Message-ID: <1366224294.9379.32.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <CAJZOPZJHJ0qKJo=HyEiJq1rRPXg+8bNh+8U_2WhX6FKbE2Km7A@mail.gmail.com>
On Wed, 2013-04-17 at 21:15 +0300, Or Gerlitz wrote:
> On Wed, Apr 17, 2013 at 9:06 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> > On 04/17/13 00:04, Stephen Rothwell wrote:
> >> Changes since 20130416:
>
> > on x86_64:
> > drivers/built-in.o: In function `isert_free_np':
> > ib_isert.c:(.text+0x6e8a77): undefined reference to `rdma_destroy_id'
> [...]
>
> Nic,
>
> Yep, you need to add
>
> depends on INET && INFINIBAND_ADDR_TRANS
>
>
> to the isert Kconfig entry
>
>
> This will make sure to get the rdma_cm to be configured and builts
> whenever isert is
>
Thanks Roland & Or, fixing this up now.
--nab
next prev parent reply other threads:[~2013-04-17 18:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 7:04 linux-next: Tree for Apr 17 Stephen Rothwell
[not found] ` <20130417170450.5dd6e5f450de4d5bf197d997-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2013-04-17 18:06 ` linux-next: Tree for Apr 17 (infiniband/rdma) Randy Dunlap
[not found] ` <516EE4BD.3000200-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-04-17 18:13 ` Roland Dreier
2013-04-17 18:15 ` Or Gerlitz
2013-04-17 18:44 ` Nicholas A. Bellinger [this message]
2013-04-17 18:10 ` linux-next: Tree for Apr 17 (kvm) Randy Dunlap
2013-04-17 22:55 ` David Rientjes
2013-04-17 23:12 ` [patch] x86, kvm: fix build failure with CONFIG_SMP disabled David Rientjes
2013-04-18 0:02 ` Randy Dunlap
2013-04-18 0:09 ` David Rientjes
2013-04-18 0:35 ` Zhang, Yang Z
2013-04-18 0:47 ` Randy Dunlap
2013-04-18 0:50 ` Zhang, Yang Z
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=1366224294.9379.32.camel@haakon3.risingtidesystems.com \
--to=nab@linux-iscsi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=or.gerlitz@gmail.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=target-devel@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;
as well as URLs for NNTP newsgroup(s).