From: Jakub Kicinski <kuba@kernel.org>
To: Stanislav Fomichev <sdf@google.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, corbet@lwn.net,
johannes@sipsolutions.net, stephen@networkplumber.org,
ecree.xilinx@gmail.com, benjamin.poirier@gmail.com,
idosch@idosch.org, f.fainelli@gmail.com, jiri@resnulli.us,
dsahern@kernel.org, fw@strlen.de, linux-doc@vger.kernel.org,
jhs@mojatatu.com, tgraf@suug.ch, jacob.e.keller@intel.com,
svinota.saveliev@gmail.com
Subject: Re: [PATCH net-next 2/2] docs: netlink: basic introduction to Netlink
Date: Thu, 18 Aug 2022 20:13:45 -0700 [thread overview]
Message-ID: <20220818201345.7b523818@kernel.org> (raw)
In-Reply-To: <CAKH8qBv7zoD6NyYBUeb3o9KjG2KpX8iw8aCpNNsoUa=oJA=VsA@mail.gmail.com>
On Wed, 17 Aug 2022 21:05:21 -0700 Stanislav Fomichev wrote:
> > +Most of the concepts and examples here refer to the ``NETLINK_ROUTE`` family,
> > +which covers much of the configuration of the Linux networking stack.
> > +Real documentation of that family, deserves a chapter (or a book) of its own.
>
> I'm assuming the answer is "no", but nonetheless: is it possible to
> use classic families over generic netlink (discover/get policy/etc)?
Not as far as I know.
> So we can just assume everything is genetlink and safely ignore all
> old quirks of the classic variant?
The behavior may differ a little with older families when it comes to
validation but yes, for the most part genetlink users should be able
to ignore all the quirks.
next prev parent reply other threads:[~2022-08-19 3:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 2:35 [PATCH net-next 1/2] net: improve and fix netlink kdoc Jakub Kicinski
2022-08-18 2:35 ` [PATCH net-next 2/2] docs: netlink: basic introduction to Netlink Jakub Kicinski
2022-08-18 4:05 ` Stanislav Fomichev
2022-08-19 3:13 ` Jakub Kicinski [this message]
2022-08-18 7:36 ` Johannes Berg
2022-08-19 16:20 ` Jakub Kicinski
2022-08-19 16:57 ` Johannes Berg
2022-08-19 17:54 ` Jakub Kicinski
2022-08-19 19:07 ` Johannes Berg
2022-08-19 19:16 ` Jakub Kicinski
2022-08-19 19:16 ` Jakub Kicinski
2022-08-19 19:20 ` Johannes Berg
2022-08-18 21:01 ` Keller, Jacob E
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=20220818201345.7b523818@kernel.org \
--to=kuba@kernel.org \
--cc=benjamin.poirier@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=ecree.xilinx@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=fw@strlen.de \
--cc=idosch@idosch.org \
--cc=jacob.e.keller@intel.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=stephen@networkplumber.org \
--cc=svinota.saveliev@gmail.com \
--cc=tgraf@suug.ch \
/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).