From: Jakub Kicinski <kuba@kernel.org>
To: "Lin Ma" <linma@zju.edu.cn>
Cc: corbet@lwn.net, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, rdunlap@infradead.org, void@manifault.com,
jani.nikula@intel.com, horms@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v3] docs: net: add netlink attrs best practices
Date: Mon, 14 Aug 2023 08:53:18 -0700 [thread overview]
Message-ID: <20230814085318.090c832d@kernel.org> (raw)
In-Reply-To: <54e9d6f6.106b1a.189e798f8ae.Coremail.linma@zju.edu.cn>
On Sat, 12 Aug 2023 10:35:09 +0800 (GMT+08:00) Lin Ma wrote:
> Moving forward, I suggest we consider the following options:
>
> 1. Update the document to address the confusion and make it more relevant
> to the current state of Netlink development. Maybe the newly added
> section seems not enough for that. I would greatly appreciate any
> specific guidance.
Unless we have docs for kernel side of modern genetlink any sort of
indication that this doc is only a guide for looking at old code will
fall on deaf ears.
So you'd need to write a sample family and docs for modern stuff.
> 2. If the document is deemed too outdated for being kernel documentation,
> maybe I should publish it somewhere else. Do you have any
> recommendations on where it could be better suited?
GitHub comes to mind for publishing ReST docs, in the meantime?
next prev parent reply other threads:[~2023-08-14 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 3:15 [PATCH v3] docs: net: add netlink attrs best practices Lin Ma
2023-08-11 17:51 ` Randy Dunlap
2023-08-12 2:12 ` Lin Ma
2023-08-11 22:26 ` Jakub Kicinski
2023-08-12 2:35 ` Lin Ma
2023-08-14 15:53 ` Jakub Kicinski [this message]
2023-08-15 17:04 ` Lin Ma
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=20230814085318.090c832d@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jani.nikula@intel.com \
--cc=linma@zju.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=void@manifault.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).