From: Jakub Kicinski <kuba@kernel.org>
To: arnd@kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
arnd@arndb.de, tariqt@nvidia.com, leon@kernel.org,
mbloch@nvidia.com, jianbol@nvidia.com,
linux-kernel@vger.kernel.org, pabeni@redhat.com,
saeedm@nvidia.com, davem@davemloft.net, andrew+netdev@lunn.ch,
raeds@nvidia.com, edumazet@google.com,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
cratiu@nvidia.com
Subject: Re: [net-next] net/mlx5e: fix ip6_dst_lookup link failure
Date: Thu, 5 Feb 2026 18:09:56 -0800 [thread overview]
Message-ID: <20260206020956.3176617-1-kuba@kernel.org> (raw)
In-Reply-To: <20260204130057.4107804-1-arnd@kernel.org>
This is an AI-generated review of your patch. The human sending this
email has considered the AI review valid, or at least plausible.
For local reproduction steps see https://netdev-ai.bots.linux.dev/ai-local.html
---
net/mlx5e: fix ip6_dst_lookup link failure
This commit adds a Kconfig dependency to prevent a link failure when IPv6
is a loadable module but mlx5 ipsec support is built-in.
Fixes: e35d7da8dd9e ("net/mlx5e: Use ip6_dst_lookup instead of ipv6_dst_lookup_flow for MAC init")
> Add a Kconfig dependency that removes avoids this configuration.
This isn't a bug, but "removes avoids" appears to be an editing artifact
where two verbs were left in place of one.
--
pw-bot: cr
next prev parent reply other threads:[~2026-02-06 2:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 13:00 [PATCH] [net-next] net/mlx5e: fix ip6_dst_lookup link failure Arnd Bergmann
2026-02-06 2:09 ` Jakub Kicinski [this message]
2026-02-06 9:56 ` Jianbo Liu
2026-02-06 10:00 ` Arnd Bergmann
2026-02-06 11:45 ` Jianbo Liu
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=20260206020956.3176617-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jianbol@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raeds@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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