From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Breno Leitao <leitao@debian.org>
Cc: fw@strlen.de, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, rbc@meta.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next v5 0/2] netfilter: Make IP_NF_IPTABLES_LEGACY selectable
Date: Wed, 18 Sep 2024 13:13:29 +0200 [thread overview]
Message-ID: <Zuq12avxPonafdvv@calendula> (raw)
In-Reply-To: <20240909084620.3155679-1-leitao@debian.org>
On Mon, Sep 09, 2024 at 01:46:17AM -0700, Breno Leitao wrote:
> These two patches make IP_NF_IPTABLES_LEGACY and IP6_NF_IPTABLES_LEGACY
> Kconfigs user selectable, avoiding creating an extra dependency by
> enabling some other config that would select IP{6}_NF_IPTABLES_LEGACY.
This needs a v6. There is also:
BRIDGE_NF_EBTABLES_LEGACY
We have more copy and paste in the bridge.
Would you submit a single patch covering this too?
next prev parent reply other threads:[~2024-09-18 11:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 8:46 [PATCH nf-next v5 0/2] netfilter: Make IP_NF_IPTABLES_LEGACY selectable Breno Leitao
2024-09-09 8:46 ` [PATCH nf-next v5 1/2] netfilter: Make IP6_NF_IPTABLES_LEGACY selectable Breno Leitao
2024-09-11 22:12 ` Pablo Neira Ayuso
2024-09-12 12:14 ` Breno Leitao
2024-09-09 8:46 ` [PATCH nf-next v5 2/2] netfilter: Make IP_NF_IPTABLES_LEGACY selectable Breno Leitao
2024-09-11 15:25 ` [PATCH nf-next v5 0/2] " Breno Leitao
2024-09-11 22:09 ` Pablo Neira Ayuso
2024-09-12 12:18 ` Breno Leitao
2024-09-15 21:07 ` Pablo Neira Ayuso
2024-09-18 11:13 ` Pablo Neira Ayuso [this message]
2024-09-18 11:21 ` Pablo Neira Ayuso
2024-09-26 11:11 ` Breno Leitao
2024-09-26 15:18 ` Pablo Neira Ayuso
2024-09-19 9:31 ` Breno Leitao
2024-09-19 10:08 ` 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=Zuq12avxPonafdvv@calendula \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rbc@meta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.