From: R SUNDAR <prosunofficial@gmail.com>
To: jmaloy@redhat.com, ying.xue@windriver.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org, R SUNDAR <prosunofficial@gmail.com>
Subject: [PATCH] Removed inputq,namedq field description to prevent kernel doc warnings.
Date: Sun, 3 Mar 2024 20:09:19 +0530 [thread overview]
Message-ID: <20240303143919.6903-1-prosunofficial@gmail.com> (raw)
./net/tipc/node.c:150: warning: Excess struct member 'inputq' description in 'tipc_node'
./net/tipc/node.c:150: warning: Excess struct member 'namedq' description in 'tipc_node'
Signed-off-by: R SUNDAR <prosunofficial@gmail.com>
---
net/tipc/node.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/net/tipc/node.c b/net/tipc/node.c
index 3105abe97bb9..c1e890a82434 100644
--- a/net/tipc/node.c
+++ b/net/tipc/node.c
@@ -86,8 +86,6 @@ struct tipc_bclink_entry {
* @lock: rwlock governing access to structure
* @net: the applicable net namespace
* @hash: links to adjacent nodes in unsorted hash chain
- * @inputq: pointer to input queue containing messages for msg event
- * @namedq: pointer to name table input queue with name table messages
* @active_links: bearer ids of active links, used as index into links[] array
* @links: array containing references to all links to node
* @bc_entry: broadcast link entry
--
2.34.1
next reply other threads:[~2024-03-03 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 14:39 R SUNDAR [this message]
2024-03-03 16:41 ` [PATCH] Removed inputq,namedq field description to prevent kernel doc warnings Randy Dunlap
2024-03-04 17:32 ` Simon Horman
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=20240303143919.6903-1-prosunofficial@gmail.com \
--to=prosunofficial@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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 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).