From: Florian Westphal <fw@strlen.de>
To: "Remy D. Farley" <one-d-wide@protonmail.com>
Cc: Donald Hunter <donald.hunter@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Phil Sutter <phil@nwl.cc>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [PATCH v6 5/6] doc/netlink: nftables: Add getcompat operation
Date: Tue, 27 Jan 2026 14:00:27 +0100 [thread overview]
Message-ID: <aXi26_vIXqQPhopG@strlen.de> (raw)
In-Reply-To: <2mi8BfZGa57pxicf4pXNT_oDJ3bvV7pByJOBhG8e7u_3eBbjubS3YJ88xHp4oDiMi3iY20zcG6FgF8_m5nsJJ_3CYHNftjAL_4EAqN5zeU0=@protonmail.com>
Remy D. Farley <one-d-wide@protonmail.com> wrote:
> > Its used by compatibility mode, it requires an nft binary linked
> > to libxtables, native nftables doesn't need it.
> >
> > I would prefer not to mention its existence.
>
> Ah, I see. Netlink-bindings have a tool to decode netlink communication, so
> it's a bit awkward to show a bunch of unkown-operations on a common command.
> I'm fine keeping it downstream.
No, showing unknown-operations is even worse.
Maybe just document in commit message that this is to avoid
clutter and present something more readable.
And perhaps mention that this is only for iptables-nft in the yaml file too.
(nft uses it on 'nft list' only if it encounters a rule added by iptables-nft).
next prev parent reply other threads:[~2026-01-27 13:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 18:47 [PATCH v6 0/6] doc/netlink: Expand nftables specification Remy D. Farley
2026-01-21 18:47 ` [PATCH v6 1/6] doc/netlink: netlink-raw: Add max check Remy D. Farley
2026-01-27 10:59 ` Donald Hunter
2026-01-21 18:47 ` [PATCH v6 2/6] doc/netlink: nftables: Add definitions Remy D. Farley
2026-01-27 11:20 ` Donald Hunter
2026-01-21 18:47 ` [PATCH v6 3/6] doc/netlink: nftables: Update attribute sets Remy D. Farley
2026-01-27 11:23 ` Donald Hunter
2026-01-21 18:47 ` [PATCH v6 4/6] doc/netlink: nftables: Add sub-messages Remy D. Farley
2026-01-27 11:27 ` Donald Hunter
2026-01-21 18:47 ` [PATCH v6 5/6] doc/netlink: nftables: Add getcompat operation Remy D. Farley
2026-01-27 9:40 ` Paolo Abeni
2026-01-27 11:32 ` Florian Westphal
2026-01-27 12:14 ` Remy D. Farley
2026-01-27 12:33 ` Florian Westphal
2026-01-27 12:44 ` Remy D. Farley
2026-01-27 13:00 ` Florian Westphal [this message]
2026-01-27 13:22 ` Remy D. Farley
2026-01-27 14:10 ` Florian Westphal
2026-01-21 18:47 ` [PATCH v6 6/6] doc/netlink: nftables: Fill out operation attributes Remy D. Farley
2026-01-27 10:58 ` [PATCH v6 0/6] doc/netlink: Expand nftables specification Donald Hunter
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=aXi26_vIXqQPhopG@strlen.de \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=donald.hunter@gmail.com \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=one-d-wide@protonmail.com \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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