From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Arnd Bergmann <arnd@arndb.de>, "David S. Miller" <davem@davemloft.net>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Greg Thelen <gthelen@google.com>,
Ka-Cheong Poon <ka-cheong.poon@oracle.com>,
Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
rds-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rds: fix building with IPV6=m
Date: Tue, 14 Aug 2018 09:53:11 -0700 [thread overview]
Message-ID: <73b656f7-ce61-b4f7-a76d-cc099bb3820f@oracle.com> (raw)
In-Reply-To: <20180814090752.1681486-1-arnd@arndb.de>
On 8/14/2018 2:07 AM, Arnd Bergmann wrote:
> When CONFIG_RDS_TCP is built-in and CONFIG_IPV6 is a loadable
> module, we get a link error agains the modular ipv6_chk_addr()
> function:
>
> net/rds/tcp.o: In function `rds_tcp_laddr_check':
> tcp.c:(.text+0x3b2): undefined reference to `ipv6_chk_addr'
>
> This adds back a dependency that forces RDS_TCP to also be
> a loadable module when IPV6 is one.
>
> Fixes: e65d4d96334e ("rds: Remove IPv6 dependency")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> net/rds/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/net/rds/Kconfig b/net/rds/Kconfig
> index 41f75563b54b..01b3bd6a3708 100644
> --- a/net/rds/Kconfig
> +++ b/net/rds/Kconfig
> @@ -16,6 +16,7 @@ config RDS_RDMA
> config RDS_TCP
> tristate "RDS over TCP"
> depends on RDS
> + depends on IPV6 || !IPV6
> ---help---
> Allow RDS to use TCP as a transport.
> This transport does not support RDMA operations.
>
Its weird depends on but probably ok since we get to module
to be enabled with or without IPV6.
Thanks for the patch Arnd !!
Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
next prev parent reply other threads:[~2018-08-14 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 9:07 [PATCH] rds: fix building with IPV6=m Arnd Bergmann
2018-08-14 16:53 ` Santosh Shilimkar [this message]
2018-08-14 17:06 ` David Miller
2018-08-14 19:15 ` Greg Thelen
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=73b656f7-ce61-b4f7-a76d-cc099bb3820f@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=gthelen@google.com \
--cc=ka-cheong.poon@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=stephen@networkplumber.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).