From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net,
imagedong@tencent.com, edumazet@google.com, dsahern@kernel.org,
talalahmad@google.com, linux-doc@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>
Subject: [RFC net-next 0/3] docs: document some aspects of struct sk_buff
Date: Wed, 23 Mar 2022 16:37:12 -0700 [thread overview]
Message-ID: <20220323233715.2104106-1-kuba@kernel.org> (raw)
I dusted off some old skb documentation patches I had in my tree.
This small set creates a place to render such documentation,
documents one random thing (data-only skbs) and converts the big
checksum comment to kdoc.
Jakub Kicinski (3):
skbuff: add a basic intro doc
skbuff: rewrite the doc for data-only skbs
skbuff: render the checksum comment to documentation
Documentation/networking/index.rst | 1 +
Documentation/networking/skbuff.rst | 37 ++++
include/linux/skbuff.h | 292 ++++++++++++++++++----------
3 files changed, 224 insertions(+), 106 deletions(-)
create mode 100644 Documentation/networking/skbuff.rst
--
2.34.1
next reply other threads:[~2022-03-23 23:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 23:37 Jakub Kicinski [this message]
2022-03-23 23:37 ` [RFC net-next 1/3] skbuff: add a basic intro doc Jakub Kicinski
2022-03-24 14:16 ` Jonathan Corbet
2022-03-24 18:20 ` Jakub Kicinski
2022-03-23 23:37 ` [RFC net-next 2/3] skbuff: rewrite the doc for data-only skbs Jakub Kicinski
2022-03-24 8:50 ` Paolo Abeni
2022-03-24 18:31 ` Jakub Kicinski
2022-03-23 23:37 ` [RFC net-next 3/3] skbuff: render the checksum comment to documentation 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=20220323233715.2104106-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=imagedong@tencent.com \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=talalahmad@google.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).