From: Linus Torvalds <torvalds@linux-foundation.org>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"general@lists.openfabrics.org" <general@lists.openfabrics.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [ofa-general] Re: linux-next: origin tree build failure
Date: Mon, 29 Dec 2008 13:07:16 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0812291304471.3082@localhost.localdomain> (raw)
In-Reply-To: <adaljtyu45d.fsf@cisco.com>
On Mon, 29 Dec 2008, Roland Dreier wrote:
>
> Something like the following maybe? (This turns off the RDMA CM if
> INFINIBAND=y and IPV6=m -- another possibility would be to just turn off
> RDMA CM IPv6 support in the case that IB is build-in but IPv6 is
> modular, but that seems like a worse idea overall)
>
> diff --git a/drivers/infiniband/Kconfig b/drivers/infiniband/Kconfig
> index a5dc78a..538a0ba 100644
> --- a/drivers/infiniband/Kconfig
> +++ b/drivers/infiniband/Kconfig
> @@ -36,7 +36,7 @@ config INFINIBAND_USER_MEM
>
> config INFINIBAND_ADDR_TRANS
> bool
> - depends on INET
> + depends on INET && !(INFINIBAND = y && IPV6 = m)
> default y
I'd suggest
config IF_IPV6
bool
depends on INET
depends on !(INFINIBAND = y && IPV6 = m)
default y
and then you can use it not only for the above:
config INFINIBAND_ADDR_TRANS
bool
depends on IF_IPV6
default y
but also use it in the source code as a more readable version:
> diff --git a/drivers/infiniband/core/addr.c b/drivers/infiniband/core/addr.c
> index d98b05b..ec7abb5 100644
> --- a/drivers/infiniband/core/addr.c> +++ b/drivers/infiniband/core/addr.c
> @@ -128,6 +128,7 @@ int rdma_translate_ip(struct sockaddr *addr, struct rdma_dev_addr *dev_addr)
> ret = rdma_copy_addr(dev_addr, dev, NULL);
> dev_put(dev);
> break;
> +#if defined(CONFIG_IPV6) || defined(CONFIG_IPV6_MODULE)
ie use
#ifdef CONFIG_IF_IPV6
here instead.
Linus
next prev parent reply other threads:[~2008-12-29 21:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 0:43 linux-next: origin tree build failure Stephen Rothwell
2008-12-29 3:36 ` Roland Dreier
2008-12-29 3:44 ` Roland Dreier
2008-12-29 9:58 ` Aleksey Senin
2008-12-29 16:13 ` [ofa-general] " Roland Dreier
2008-12-29 16:52 ` Aleksey Senin
2008-12-29 20:18 ` Roland Dreier
2008-12-29 21:07 ` Linus Torvalds [this message]
2008-12-29 21:35 ` Roland Dreier
2008-12-29 21:48 ` Roland Dreier
2008-12-29 8:48 ` Aleksey Senin
2008-12-30 7:38 ` Roland Dreier
2008-12-30 8:30 ` Stephen Rothwell
2008-12-30 15:41 ` Roland Dreier
2008-12-30 15:46 ` Stephen Rothwell
2008-12-30 22:52 ` Stephen Rothwell
2008-12-30 22:56 ` Roland Dreier
2008-12-30 23:17 ` Stephen Rothwell
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=alpine.LFD.2.00.0812291304471.3082@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=sfr@canb.auug.org.au \
/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