From: Fernando Fernandez Mancera <fmancera@suse.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, dsahern@kernel.org,
rbm@suse.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/10 net-next v3] Convert CONFIG_IPV6 to built-in and remove stubs
Date: Thu, 19 Mar 2026 09:28:54 +0100 [thread overview]
Message-ID: <66cfa9d9-760a-4ef0-8139-cd7f27115f09@suse.de> (raw)
In-Reply-To: <20260318174812.2dafba4d@kernel.org>
On 3/19/26 1:48 AM, Jakub Kicinski wrote:
> On Wed, 18 Mar 2026 16:21:34 -0700 Jakub Kicinski wrote:
>>> This is test is applying the series in top of bpf tree which has this
>>> commit
>>> https://github.com/kernel-patches/bpf/commit/972787479ee73006fddb5e59ab5c8e733810ff42
>>>
>>> AFAICS, net-next tree do not have it yet. I do not think I can do much
>>> about it for now. Will wait until they are merged and rebase in top of it.
>>
>> I see, hopefully trees converge tomorrow, else we can fix it when
>> merging.
>
> Looking closer and talking to Alexei the fix is actually in bpf-next
> not in bpf. So let's just merge your code and we'll deal with the
> fallout. But please still look into the fowarding warnings, of course.
>
Yes I already handled the forwarding warnings. I am surprised this
wasn't spotted by the AI :/
Thanks,
Fernando.
prev parent reply other threads:[~2026-03-19 8:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 14:00 [PATCH 00/10 net-next v3] Convert CONFIG_IPV6 to built-in and remove stubs Fernando Fernandez Mancera
2026-03-17 14:00 ` [PATCH 01/10 net-next v3] ipv6: convert CONFIG_IPV6 to built-in only and clean up Kconfigs Fernando Fernandez Mancera
2026-03-18 6:51 ` Krzysztof Kozlowski
2026-03-18 9:50 ` Ricardo B. Marlière
2026-03-18 10:14 ` Fernando Fernandez Mancera
2026-03-18 10:17 ` Krzysztof Kozlowski
2026-03-17 14:00 ` [PATCH 02/10 net-next v3] ipv6: replace IS_BUILTIN(CONFIG_IPV6) with IS_ENABLED(CONFIG_IPV6) Fernando Fernandez Mancera
2026-03-17 14:00 ` [PATCH 03/10 net-next v3] ipv6: remove dynamic ICMPv6 sender registration infrastructure Fernando Fernandez Mancera
2026-03-17 14:01 ` [PATCH 04/10 net-next v3] ipv6: prepare headers for ipv6_stub removal Fernando Fernandez Mancera
2026-03-17 20:12 ` Ido Schimmel
2026-03-18 10:43 ` Fernando Fernandez Mancera
2026-03-18 12:45 ` Ido Schimmel
2026-03-18 13:01 ` Fernando Fernandez Mancera
2026-03-17 14:01 ` [PATCH 05/10 net-next v3] drivers: net: drop ipv6_stub usage and use direct function calls Fernando Fernandez Mancera
2026-03-17 14:01 ` [PATCH 06/10 net-next v3] ipv4: " Fernando Fernandez Mancera
2026-03-17 14:01 ` [PATCH 07/10 net-next v3] net: convert remaining ipv6_stub users to " Fernando Fernandez Mancera
2026-03-17 14:01 ` [PATCH 08/10 net-next v3] bpf: remove ipv6_bpf_stub completely and use " Fernando Fernandez Mancera
2026-03-17 14:01 ` [PATCH 09/10 net-next v3] ipv6: remove ipv6_stub infrastructure completely Fernando Fernandez Mancera
2026-03-17 14:01 ` [PATCH 10/10 net-next v3] netfilter: remove nf_ipv6_ops and use direct function calls Fernando Fernandez Mancera
2026-03-17 20:17 ` Ido Schimmel
2026-03-18 12:18 ` Fernando Fernandez Mancera
2026-03-17 19:49 ` [PATCH 00/10 net-next v3] Convert CONFIG_IPV6 to built-in and remove stubs Jakub Kicinski
2026-03-18 10:19 ` Fernando Fernandez Mancera
2026-03-18 23:21 ` Jakub Kicinski
2026-03-19 0:48 ` Jakub Kicinski
2026-03-19 8:28 ` Fernando Fernandez Mancera [this message]
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=66cfa9d9-760a-4ef0-8139-cd7f27115f09@suse.de \
--to=fmancera@suse.de \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rbm@suse.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