From: Jakub Kicinski <kuba@kernel.org>
To: Florian Westphal <fw@strlen.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Ahern <dsahern@kernel.org>,
coreteam@netfilter.org,
"netdev-driver-reviewers@vger.kernel.org"
<netdev-driver-reviewers@vger.kernel.org>,
Hangbin Liu <liuhangbin@gmail.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [netfilter-core] [ANN] net-next is OPEN
Date: Thu, 25 Jan 2024 09:30:30 -0800 [thread overview]
Message-ID: <20240125093030.1ced969e@kernel.org> (raw)
In-Reply-To: <20240125085211.GE31645@breakpoint.cc>
On Thu, 25 Jan 2024 09:52:11 +0100 Florian Westphal wrote:
> > NFT_COMPAT fixed a lot! One remaining warning comes from using
> > -m length. Which NFT config do we need for that one?
>
> CONFIG_NETFILTER_XT_MATCH_LENGTH=m|y
Thank you, that seems to solve the remaining problem!
next prev parent reply other threads:[~2024-01-25 17:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240122091612.3f1a3e3d@kernel.org>
[not found] ` <Za98C_rCH8iO_yaK@Laptop-X1>
[not found] ` <20240123072010.7be8fb83@kernel.org>
[not found] ` <d0e28c67-51ad-4da1-a6df-7ebdbd45cd2b@kernel.org>
[not found] ` <65b133e83f53e_225ba129414@willemb.c.googlers.com.notmuch>
[not found] ` <20240124082255.7c8f7c55@kernel.org>
2024-01-24 17:01 ` [ANN] net-next is OPEN Jakub Kicinski
2024-01-24 18:35 ` Matthieu Baerts
2024-01-24 19:00 ` Jakub Kicinski
2024-01-24 19:18 ` [netfilter-core] " Pablo Neira Ayuso
2024-02-06 18:31 ` Matthieu Baerts
2024-02-07 9:49 ` Pablo Neira Ayuso
2024-02-07 11:33 ` Matthieu Baerts
2024-02-16 15:38 ` Pablo Neira Ayuso
2024-02-16 15:51 ` Matthieu Baerts
2024-01-24 19:16 ` Pablo Neira Ayuso
2024-01-24 19:40 ` Jakub Kicinski
2024-01-24 20:02 ` Pablo Neira Ayuso
2024-01-24 20:13 ` Jakub Kicinski
2024-01-25 5:07 ` Jakub Kicinski
2024-01-25 8:52 ` Florian Westphal
2024-01-25 17:30 ` Jakub Kicinski [this message]
2024-01-25 9:29 ` Pablo Neira Ayuso
2024-01-25 17:34 ` 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=20240125093030.1ced969e@kernel.org \
--to=kuba@kernel.org \
--cc=coreteam@netfilter.org \
--cc=dsahern@kernel.org \
--cc=fw@strlen.de \
--cc=liuhangbin@gmail.com \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=willemdebruijn.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).