From: Kalle Valo <kvalo@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Prameela Rani Garnepudi <prameela.j04cs@gmail.com>,
Siva Rebbagondla <siva.rebbagondla@redpinesignals.com>,
Amitkumar Karwar <amit.karwar@redpinesignals.com>
Subject: Re: [PATCH net 12/12] rsi: remove kernel-doc comment marker
Date: Tue, 11 Jul 2023 11:58:42 +0300 [thread overview]
Message-ID: <878rbm964d.fsf@kernel.org> (raw)
In-Reply-To: <20230710230312.31197-13-rdunlap@infradead.org> (Randy Dunlap's message of "Mon, 10 Jul 2023 16:03:12 -0700")
Randy Dunlap <rdunlap@infradead.org> writes:
> Change an errant kernel-doc comment marker (/**) to a regular
> comment to prevent a kernel-doc warning.
>
> rsi_91x.h:3: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
> * Copyright (c) 2017 Redpine Signals Inc.
>
> Fixes: 4c10d56a76bb ("rsi: add header file rsi_91x")
> 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: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>
> Cc: Siva Rebbagondla <siva.rebbagondla@redpinesignals.com>
> Cc: Amitkumar Karwar <amit.karwar@redpinesignals.com>
> Cc: Kalle Valo <kvalo@kernel.org>
As wireless trees are closed for July please take this to net tree:
Acked-by: Kalle Valo <kvalo@kernel.org>
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-07-11 8:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 23:03 [PATCH net 00/12] net: fix kernel-doc problems in include/net/ Randy Dunlap
2023-07-10 23:03 ` [PATCH net 01/12] net: bonding: remove kernel-doc comment marker Randy Dunlap
2023-07-10 23:03 ` [PATCH net 02/12] wifi: cfg80211: remove dead/unused enum value Randy Dunlap
2023-07-10 23:03 ` [PATCH net 03/12] net: cfg802154: fix kernel-doc notation warnings Randy Dunlap
2023-07-11 8:36 ` Miquel Raynal
2023-07-10 23:03 ` [PATCH net 04/12] codel: " Randy Dunlap
2023-07-10 23:03 ` [PATCH net 05/12] devlink: " Randy Dunlap
2023-07-10 23:03 ` [PATCH net 06/12] wifi: radiotap: " Randy Dunlap
2023-07-10 23:03 ` [PATCH net 07/12] inet: frags: remove kernel-doc comment marker Randy Dunlap
2023-07-12 3:34 ` Jakub Kicinski
2023-07-12 3:48 ` Randy Dunlap
2023-07-10 23:03 ` [PATCH net 08/12] net: llc: fix kernel-doc notation warnings Randy Dunlap
2023-07-10 23:03 ` [PATCH net 09/12] wifi: mac80211: fix kernel-doc notation warning Randy Dunlap
2023-07-12 3:37 ` Jakub Kicinski
2023-07-12 3:46 ` Randy Dunlap
2023-07-10 23:03 ` [PATCH net 10/12] net: NSH: " Randy Dunlap
2023-07-10 23:03 ` [PATCH net 11/12] pie: " Randy Dunlap
2023-07-10 23:03 ` [PATCH net 12/12] rsi: remove kernel-doc comment marker Randy Dunlap
2023-07-11 8:58 ` Kalle Valo [this message]
2023-07-12 3:37 ` 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=878rbm964d.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=amit.karwar@redpinesignals.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prameela.j04cs@gmail.com \
--cc=rdunlap@infradead.org \
--cc=siva.rebbagondla@redpinesignals.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.