From: Jakub Kicinski <kuba@kernel.org>
To: "Remy D. Farley" <one-d-wide@protonmail.com>
Cc: Donald Hunter <donald.hunter@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH v2] doc/netlink: Expand nftables specificaion
Date: Fri, 3 Oct 2025 14:04:02 -0700 [thread overview]
Message-ID: <20251003140402.1c5bef8d@kernel.org> (raw)
In-Reply-To: <20251003175510.1074239-1-one-d-wide@protonmail.com>
On Fri, 03 Oct 2025 17:55:34 +0000 Remy D. Farley wrote:
> Getting out changes I've accumulated while making nftables spec to work with
> Rust netlink-bindings. Hopefully, this will be useful upstream.
>
> This patch:
>
> - Adds missing byte order annotations.
> - Fills out attributes in some operations.
> - Replaces non-existent "name" attribute with todo comment.
> - Adds some missing sub-messages (and associated attributes).
> - Adds (copies over) documentation for some attributes / enum entries.
> - Adds "getcompat" operation defined in nft_compat.c .
> - Allows ynl_gen_rst.py script to handle empty request/reply attribute.
Please don't send a reply in a previous thread and 4 min later a new
version of the patch :(
BTW this doesn't apply to net-next.
prev parent reply other threads:[~2025-10-03 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 17:55 [PATCH v2] doc/netlink: Expand nftables specificaion Remy D. Farley
2025-10-03 21:04 ` Jakub Kicinski [this message]
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=20251003140402.1c5bef8d@kernel.org \
--to=kuba@kernel.org \
--cc=donald.hunter@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=one-d-wide@protonmail.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).