From: Jakub Kicinski <kuba@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Nikolay Aleksandrov <razor@blackwall.org>
Subject: Re: [PATCH v2 net 07/12] inet: frags: eliminate kernel-doc warning
Date: Wed, 12 Jul 2023 17:16:37 -0700 [thread overview]
Message-ID: <20230712171637.5c9630b9@kernel.org> (raw)
In-Reply-To: <20230712044040.10723-1-rdunlap@infradead.org>
On Tue, 11 Jul 2023 21:40:40 -0700 Randy Dunlap wrote:
> Change the anonymous enum kernel-doc content so that it doesn't cause
> a kernel-doc warning.
>
> inet_frag.h:33: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
Could you resend the entire series with the more complex WiFi patches
taken out as well?
next prev parent reply other threads:[~2023-07-13 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 4:40 [PATCH v2 net 07/12] inet: frags: eliminate kernel-doc warning Randy Dunlap
2023-07-13 0:16 ` Jakub Kicinski [this message]
2023-07-13 2:46 ` 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=20230712171637.5c9630b9@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--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 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.