From: Florian Westphal <fw@strlen•de>
To: Breno Leitao <leitao@debian•org>
Cc: Florian Westphal <fw@strlen•de>,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, Pablo Neira Ayuso <pablo@netfilter•org>,
Jozsef Kadlecsik <kadlec@netfilter•org>,
David Ahern <dsahern@kernel•org>,
rbc@meta•com, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org, netfilter-devel@vger•kernel.org,
"open list:NETFILTER" <coreteam@netfilter•org>
Subject: Re: [PATCH nf-next v4 1/2] netfilter: Make IP6_NF_IPTABLES_LEGACY selectable
Date: Fri, 30 Aug 2024 16:09:10 +0200 [thread overview]
Message-ID: <20240830140910.GA30623@breakpoint.cc> (raw)
In-Reply-To: <ZtHRZwYGQDVueUlY@gmail.com>
Breno Leitao <leitao@debian•org> wrote:
> > I thunk patch is fine, I will try to add the relevant
> > depends-on change some time in the near future.
>
> I am more than happy to do it, if you wish. I just want to decouple both
> changes from each other.
Ah, that makes sense to me.
The "depends" change would be good to have, see
https://lore.kernel.org/netfilter-devel/20240813183202.GA13864@breakpoint.cc/
(TL;DR: PREEMPT_RT requirements would need more surgery in old
x_tables infra)
next prev parent reply other threads:[~2024-08-30 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 16:16 [PATCH nf-next v4 0/2] netfilter: Make IP_NF_IPTABLES_LEGACY selectable Breno Leitao
2024-08-29 16:16 ` [PATCH nf-next v4 1/2] netfilter: Make IP6_NF_IPTABLES_LEGACY selectable Breno Leitao
2024-08-29 16:25 ` Florian Westphal
2024-08-30 12:45 ` Breno Leitao
2024-08-30 13:13 ` Florian Westphal
2024-08-30 14:04 ` Breno Leitao
2024-08-30 14:09 ` Florian Westphal [this message]
2024-09-05 23:01 ` Pablo Neira Ayuso
2024-09-09 8:29 ` Breno Leitao
2024-08-29 16:16 ` [PATCH nf-next v4 2/2] netfilter: Make IP_NF_IPTABLES_LEGACY selectable Breno Leitao
2024-08-30 18:18 ` [PATCH nf-next v4 0/2] " 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=20240830140910.GA30623@breakpoint.cc \
--to=fw@strlen$(echo .)de \
--cc=coreteam@netfilter$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=kadlec@netfilter$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=leitao@debian$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pablo@netfilter$(echo .)org \
--cc=rbc@meta$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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