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] doc/netlink: Expand nftables specification
Date: Fri, 3 Oct 2025 11:05:35 -0700 [thread overview]
Message-ID: <20251003110535.350f2597@kernel.org> (raw)
In-Reply-To: <JUuZco3v6YeIraurnU7qR-yqiNiPq8B5F6MJDG_2_tIrtMvkLEFhhPnns2BV7YCvAYkBLlhkadllZyRgQ7LmNWyWihwYr1dU9526sV63Ew4=@protonmail.com>
On Fri, 03 Oct 2025 17:51:54 +0000 Remy D. Farley wrote:
> Also, it caught another issue. Python yaml doesn't distinguish an empty
> attrset/list and a null-value:
>
> ```yaml
> dump: # attrset
> reply: # null (but attrset expected in code)
> # no attribute here => dump["reply"] is None
> ```
>
> I think it's useful to have a machine readable mark to signal that the
> operation supports dump flag, even though there're no attributes outlined yet.
> I fixed it by simply checking for null in ynl_gen_rst.py .
Hm, hm, hm. So for "do" we use empty replies to mean that the reply
_will actually arrive_ but it will have no attributes. Whether an
operation returns a reply or not cannot be changed once operation
was added without breaking uAPI. So the empty reply is a way for us
to "reserve" the reply because we think we may need it in the future.
Or at least that's what my faulty memory of the situation is.
What an empty dump reply is I do not know. How we could have a dump
enumerating objects without producing replies!? :$
next prev parent reply other threads:[~2025-10-03 18:05 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 [this message]
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
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=20251003110535.350f2597@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).