mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "David S. Miller" <davem@davemloft.net>,
	Simon Horman <simon.horman@netronome.com>,
	John Hurley <john.hurley@netronome.com>,
	Jiri Pirko <jiri@mellanox.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	oss-drivers@netronome.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netronome: fix ipv6 link error
Date: Tue, 7 Jan 2020 12:44:17 -0800	[thread overview]
Message-ID: <20200107124417.5239a6cf@cakuba.netronome.com> (raw)
In-Reply-To: <20200107200659.3538375-1-arnd@arndb.de>

On Tue,  7 Jan 2020 21:06:40 +0100, Arnd Bergmann wrote:
> When the driver is built-in but ipv6 is a module, the flower
> support produces a link error:
> 
> drivers/net/ethernet/netronome/nfp/flower/tunnel_conf.o: In function `nfp_tunnel_keep_alive_v6':
> tunnel_conf.c:(.text+0x2aa8): undefined reference to `nd_tbl'

Damn, I guess the v2 of that patch set did not solve _all_ v6 linking
issues :/ Thanks for the patch.

> Add a Kconfig dependency to avoid that configuration.
> 
> Fixes: 9ea9bfa12240 ("nfp: flower: support ipv6 tunnel keep-alive messages from fw")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>  drivers/net/ethernet/netronome/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/net/ethernet/netronome/Kconfig b/drivers/net/ethernet/netronome/Kconfig
> index bac5be4d4f43..dcb02ce28460 100644
> --- a/drivers/net/ethernet/netronome/Kconfig
> +++ b/drivers/net/ethernet/netronome/Kconfig
> @@ -31,6 +31,7 @@ config NFP_APP_FLOWER
>  	bool "NFP4000/NFP6000 TC Flower offload support"
>  	depends on NFP
>  	depends on NET_SWITCHDEV
> +	depends on IPV6 != m || NFP =m

Could we perhaps do the more standard:

	depends on IPV6 || IPV6=n

The whitespace around = and != seems a little random as is..

>  	default y
>  	---help---
>  	  Enable driver support for TC Flower offload on NFP4000 and NFP6000.


  reply	other threads:[~2020-01-07 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 20:06 Arnd Bergmann
2020-01-07 20:44 ` Jakub Kicinski [this message]
2020-01-07 22:01   ` Arnd Bergmann
2020-01-08 13:09     ` Jakub Kicinski

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=20200107124417.5239a6cf@cakuba.netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=jiri@mellanox.com \
    --cc=john.hurley@netronome.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.com \
    --cc=simon.horman@netronome.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

all inboxes | Powered by JetHome®