From: Jonathan Corbet <corbet@lwn.net>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, pabeni@redhat.com, imagedong@tencent.com,
edumazet@google.com, dsahern@kernel.org, talalahmad@google.com,
linux-doc@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [RFC net-next 1/3] skbuff: add a basic intro doc
Date: Thu, 24 Mar 2022 08:16:49 -0600 [thread overview]
Message-ID: <87a6dfigfi.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220323233715.2104106-2-kuba@kernel.org>
Jakub Kicinski <kuba@kernel.org> writes:
> Add basic skb documentation. It's mostly an intro to the subsequent
> patches - it would looks strange if we documented advanced topics
> without covering the basics in any way.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Glad to see improved docs! One nit...
> Documentation/networking/skbuff.rst | 25 ++++++++++++++++++
> include/linux/skbuff.h | 40 +++++++++++++++++++++++++++++
> 2 files changed, 65 insertions(+)
> create mode 100644 Documentation/networking/skbuff.rst
>
> diff --git a/Documentation/networking/skbuff.rst b/Documentation/networking/skbuff.rst
> new file mode 100644
> index 000000000000..7c6be64f486a
> --- /dev/null
> +++ b/Documentation/networking/skbuff.rst
> @@ -0,0 +1,25 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +struct sk_buff
> +==============
> +
> +:c:type:`struct sk_buff` is the main networking structure representing
> +a packet.
You shouldn't need :c:type: here, our magic stuff should see "struct
sk_buff" and generate the cross reference. Of course, it will be a
highly local reference in this case...
Thanks,
jon
next prev parent reply other threads:[~2022-03-24 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 23:37 [RFC net-next 0/3] docs: document some aspects of struct sk_buff Jakub Kicinski
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 [this message]
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=87a6dfigfi.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=imagedong@tencent.com \
--cc=kuba@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.