From: Simon Horman <horms@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH] net: skbuff: fix kernel-doc typos
Date: Tue, 3 Oct 2023 12:44:47 +0200 [thread overview]
Message-ID: <ZRvwn8lTaFxJ83X/@kernel.org> (raw)
In-Reply-To: <20231001003846.29541-2-rdunlap@infradead.org>
On Sat, Sep 30, 2023 at 05:38:46PM -0700, Randy Dunlap wrote:
> Correct punctuation.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Paolo Abeni <pabeni@redhat.com>
> Cc: netdev@vger.kernel.org
> ---
> include/linux/skbuff.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff -- a/include/linux/skbuff.h b/include/linux/skbuff.h
> --- a/include/linux/skbuff.h
> +++ b/include/linux/skbuff.h
> @@ -1309,7 +1309,7 @@ struct sk_buff_fclones {
> *
> * Returns true if skb is a fast clone, and its clone is not freed.
> * Some drivers call skb_orphan() in their ndo_start_xmit(),
> - * so we also check that this didnt happen.
> + * so we also check that this didn't happen.
At the risk of bikeshedding (let's not) perhaps "this" can be dropped
from the line above?
In any case, I agree that this patch improves the documentation.
Reviewed-by: Simon Horman <horms@kernel.org>
> */
> static inline bool skb_fclone_busy(const struct sock *sk,
> const struct sk_buff *skb)
> @@ -2016,7 +2016,7 @@ static inline struct sk_buff *skb_share_
> * Copy shared buffers into a new sk_buff. We effectively do COW on
> * packets to handle cases where we have a local reader and forward
> * and a couple of other messy ones. The normal one is tcpdumping
> - * a packet thats being forwarded.
> + * a packet that's being forwarded.
> */
>
> /**
>
next prev parent reply other threads:[~2023-10-03 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 0:38 [PATCH] page_pool: fix documentation typos Randy Dunlap
2023-10-01 0:38 ` [PATCH] net: skbuff: fix kernel-doc typos Randy Dunlap
2023-10-03 10:44 ` Simon Horman [this message]
2023-10-04 21:21 ` Jakub Kicinski
2023-10-03 10:45 ` [PATCH] page_pool: fix documentation typos Simon Horman
2023-10-03 15:29 ` Ilias Apalodimas
2023-10-04 21:30 ` 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=ZRvwn8lTaFxJ83X/@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
/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).