From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
linux-rt-devel@lists.linux.dev,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [net-next v3 0/3] Disable LEGACY iptables on PREEMPT_RT
Date: Wed, 26 Mar 2025 08:47:21 +0100 [thread overview]
Message-ID: <20250326074721.Y1sIc4Al@linutronix.de> (raw)
In-Reply-To: <20250325194804.GA18860@breakpoint.cc>
On 2025-03-25 20:48:04 [+0100], Florian Westphal wrote:
> I applied following diff on top of this series, after that
> ./iptables-test.py -n
> and
> iptables/tests/shell/run-tests.sh
>
> pass (legacy version fails as expected).
> The change in xt_mark is awkward but its the only place that
> needs it so its not worth to add a new kconfig symbol to avoid ||
> test.
Thank you. I'm going to fold this into 1/3.
Sebastian
next prev parent reply other threads:[~2025-03-26 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 16:58 [net-next v3 0/3] Disable LEGACY iptables on PREEMPT_RT Sebastian Andrzej Siewior
2025-03-25 16:58 ` [net-next v3 1/3] netfilter: replace select by depends on for IP{6}_NF_IPTABLES_LEGACY Sebastian Andrzej Siewior
2025-03-26 17:09 ` Phil Sutter
2025-03-26 17:11 ` Sebastian Andrzej Siewior
2025-03-25 16:58 ` [net-next v3 2/3] netfilter: Let IP6_NF_IPTABLES_LEGACY select IP6_NF_IPTABLES Sebastian Andrzej Siewior
2025-03-25 16:58 ` [net-next v3 3/3] netfilter: Introduce NETFILTER_LEGACY to group all legacy code Sebastian Andrzej Siewior
2025-03-25 19:48 ` [net-next v3 0/3] Disable LEGACY iptables on PREEMPT_RT Florian Westphal
2025-03-26 7:47 ` Sebastian Andrzej Siewior [this message]
2025-03-26 21:18 ` Pablo Neira Ayuso
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=20250326074721.Y1sIc4Al@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tglx@linutronix.de \
/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).