From: Donald Hunter <donald.hunter@gmail.com>
To: "Remy D. Farley" <one-d-wide@protonmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>, netdev@vger.kernel.org
Subject: Re: [PATCH] doc/netlink: Expand nftables specificaion
Date: Fri, 10 Oct 2025 10:21:23 +0100 [thread overview]
Message-ID: <m2v7knqfho.fsf@gmail.com> (raw)
In-Reply-To: <20251009203324.1444367-1-one-d-wide@protonmail.com>
"Remy D. Farley" <one-d-wide@protonmail.com> writes:
> Getting out some changes I've accumulated while making nftables to work with
> Rust netlink-bindings. Hopefully, this will be useful upstream.
>
> This patch:
>
> - Fills out missing attributes in operations.
> - Adds missing annotations: dump ops, byte-order, checks.
> - Adds some missing sub-options (and their associated attributes).
> - Adds (copying over) documentation for some attributes/enum members.
> - Adds "getcompat" operation.
> - Adds max check in netlink-raw specification (suggested by Donald Hunter).
>
> Signed-off-by: Remy D. Farley <one-d-wide@protonmail.com>
Hi Remy,
Is this v3? It should say v3 in the subject and it should contain a list
of the changes since v2 and v1. It's hard for reviewers to follow what
is going on otherwise.
https://docs.kernel.org/process/submitting-patches.html#commentary
> On Friday, October 3rd, 2025 at 9:04 PM, Jakub Kicinski <kuba@kernel.org> wrote:
>> Please don't send a reply in a previous thread and 4 min later a new
>> version of the patch :(
You did it again, reply and new patch minutes apart. The commentary in
the reply could instead have been in the changelog of this patch.
> ---
> Documentation/netlink/netlink-raw.yaml | 11 +-
> Documentation/netlink/specs/nftables.yaml | 656 ++++++++++++++++++++--
> 2 files changed, 617 insertions(+), 50 deletions(-)
I think this should a 2 patch series since the schema update is a
logical change that is independent of the nftables.yaml changes.
Also, net-next is closed until Oct 13 so you should resubmit when net-next
is open again.
https://netdev.bots.linux.dev/net-next.html
I will review the rest of the nftables.yaml changes in the meantime.
Thanks,
Donald.
prev parent reply other threads:[~2025-10-10 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 18:50 [PATCH] doc/netlink: Expand nftables specification Remy D. Farley
2025-10-02 22:11 ` Jakub Kicinski
2025-10-03 17:51 ` Remy D. Farley
2025-10-03 18:05 ` Jakub Kicinski
2025-10-06 8:27 ` Donald Hunter
2025-10-06 14:08 ` Donald Hunter
2025-10-09 20:24 ` Remy D. Farley
2025-10-09 20:33 ` [PATCH] doc/netlink: Expand nftables specificaion Remy D. Farley
2025-10-10 9:21 ` Donald Hunter [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=m2v7knqfho.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=kuba@kernel.org \
--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 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.