From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
linux-doc@vger.kernel.org, corbet@lwn.net, imagedong@tencent.com,
dsahern@gmail.com, talalahmad@google.com,
Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/3] docs: document some aspects of struct sk_buff
Date: Mon, 9 May 2022 09:04:53 -0700 [thread overview]
Message-ID: <20220509160456.1058940-1-kuba@kernel.org> (raw)
This small set creates a place to render sk_buff documentation,
documents one random thing (data-only skbs) and converts the big
checksum comment to kdoc.
RFC v2 (no changes since then):
- fix type reference in patch 1
- use "payload" and "data" more consistently
- add snippet with calls
https://lore.kernel.org/r/20220324231312.2241166-1-kuba@kernel.org/
RFC v1:
https://lore.kernel.org/all/20220323233715.2104106-1-kuba@kernel.org/
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 | 301 ++++++++++++++++++----------
3 files changed, 232 insertions(+), 107 deletions(-)
create mode 100644 Documentation/networking/skbuff.rst
--
2.34.3
next reply other threads:[~2022-05-09 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 16:04 Jakub Kicinski [this message]
2022-05-09 16:04 ` [PATCH net-next 1/3] skbuff: add a basic intro doc Jakub Kicinski
2022-05-09 16:04 ` [PATCH net-next 2/3] skbuff: rewrite the doc for data-only skbs Jakub Kicinski
2022-05-09 16:04 ` [PATCH net-next 3/3] skbuff: render the checksum comment to documentation Jakub Kicinski
2022-05-10 2:44 ` [PATCH net-next 0/3] docs: document some aspects of struct sk_buff David Ahern
2022-05-11 1:40 ` patchwork-bot+netdevbpf
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=20220509160456.1058940-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--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).