From: Lothar Rubusch <l.rubusch@gmail.com>
To: kuba@kernel.org, davem@davemloft.net
Cc: netdev@vger.kernel.org, Lothar Rubusch <l.rubusch@gmail.com>
Subject: [PATCH] Documentation: sock.h - fix warnings
Date: Mon, 6 Apr 2020 21:52:30 +0000 [thread overview]
Message-ID: <20200406215230.21758-1-l.rubusch@gmail.com> (raw)
Fix some sphinx warnings at 'make htmldocs'.
Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
---
include/net/sock.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/net/sock.h b/include/net/sock.h
index 6d84784d33fa..2924bcbbd402 100644
--- a/include/net/sock.h
+++ b/include/net/sock.h
@@ -2554,8 +2554,8 @@ sk_is_refcounted(struct sock *sk)
/**
* skb_steal_sock
- * @skb to steal the socket from
- * @refcounted is set to true if the socket is reference-counted
+ * @skb: to steal the socket from
+ * @refcounted: is set to true if the socket is reference-counted
*/
static inline struct sock *
skb_steal_sock(struct sk_buff *skb, bool *refcounted)
--
2.20.1
next reply other threads:[~2020-04-06 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 21:52 Lothar Rubusch [this message]
2020-04-07 22:32 ` [PATCH] Documentation: sock.h - fix warnings Randy Dunlap
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=20200406215230.21758-1-l.rubusch@gmail.com \
--to=l.rubusch@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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).