From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, nicolas.dichtel@6wind.com, fw@strlen.de,
pablo@netfilter.org, jiri@resnulli.us, mkubecek@suse.cz,
aleksander.lobakin@intel.com, Thomas Haller <thaller@redhat.com>
Subject: Re: [RFC] netlink: add variable-length / auto integers
Date: Wed, 11 Oct 2023 09:19:59 -0700 [thread overview]
Message-ID: <20231011091959.48010d43@kernel.org> (raw)
In-Reply-To: <9c70c71cecf19a50c56ed57c0f99660a3176d11d.camel@sipsolutions.net>
On Wed, 11 Oct 2023 18:16:42 +0200 Johannes Berg wrote:
> > I was planning to add the docs to Documentation/userspace-api/netlink/
> > Is that too YNL-specific?
>
> Oh. I guess I keep expecting that header files at least have some hints,
> but whatever ... experience tells me anyway that nobody bothers reading
> the comments and people just copy stuff from elsewhere, so we just have
> to get this right first in one place ;-)
I'll try to add something in the header, in that case.
The netlink.h headers are particularly non-conducive
to finding stuff since we have 3 of them :(
next prev parent reply other threads:[~2023-10-11 16:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 0:33 [RFC] netlink: add variable-length / auto integers Jakub Kicinski
2023-10-11 13:11 ` Johannes Berg
2023-10-11 14:03 ` Nicolas Dichtel
2023-10-11 15:52 ` Jakub Kicinski
2023-10-11 16:01 ` Johannes Berg
2023-10-11 16:45 ` Stephen Hemminger
2023-10-12 9:26 ` David Laight
2023-10-12 6:47 ` Nicolas Dichtel
2023-10-11 16:08 ` Jakub Kicinski
2023-10-11 16:16 ` Johannes Berg
2023-10-11 16:19 ` Jakub Kicinski [this message]
2023-10-11 13:46 ` Jiri Pirko
2023-10-11 16:16 ` Jakub Kicinski
2023-10-11 16:21 ` Johannes Berg
2023-10-11 16:34 ` Jakub Kicinski
2023-10-11 16:37 ` Johannes Berg
2023-10-11 17:01 ` Jiri Pirko
2023-10-11 20:21 ` Jakub Kicinski
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=20231011091959.48010d43@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=fw@strlen.de \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pablo@netfilter.org \
--cc=thaller@redhat.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).