From: Randy Dunlap <rdunlap@infradead.org>
To: Alexandra Winter <wintera@linux.ibm.com>, netdev@vger.kernel.org
Cc: Thorsten Winkler <twinkler@linux.ibm.com>,
linux-s390@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH v3 net-next] net/iucv: clean up iucv kernel-doc warnings
Date: Tue, 3 Feb 2026 10:30:51 -0800 [thread overview]
Message-ID: <2dfeee9a-ea5e-4f8d-822e-d7ee84544c5e@infradead.org> (raw)
In-Reply-To: <04ce261c-2cef-4575-8e2d-e13391c2a933@linux.ibm.com>
On 2/3/26 1:39 AM, Alexandra Winter wrote:
>
>
> On 03.02.26 08:52, Randy Dunlap wrote:
>> Fix numerous (many) kernel-doc warnings in iucv.[ch]:
>>
>> - convert function documentation comments to a common (kernel-doc) look,
>> even for static functions (without "/**")
>> - use matching parameter and parameter description names
>> - use better wording in function descriptions (Jakub & AI)
>> - remove duplicate kernel-doc comments from the header file (Jakub)
>>
>> Examples:
>>
>> Warning: include/net/iucv/iucv.h:210 missing initial short description
>> on line: * iucv_unregister
>> Warning: include/net/iucv/iucv.h:216 function parameter 'handle' not
>> described in 'iucv_unregister'
>> Warning: include/net/iucv/iucv.h:467 function parameter 'answer' not
>> described in 'iucv_message_send2way'
>> Warning: net/iucv/iucv.c:727 missing initial short description on line:
>> * iucv_cleanup_queue
>>
>> Build-tested with both "make htmldocs" and "make ARCH=s390 defconfig all".
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> ---
>> v3:
>> - I didn't use Alexandra'a (v2) Reviewed-by: due to the number of changes.
>> - leave kernel-doc ("/**") on static functions in iucv.c (I did not
>> convert other static functions to kernel-doc comments.)
>
> Thank you. Feel free to add
> Reviewed-by: Alexandra Winter <wintera@linux.ibm.com>
>
>
> There are still warnings left about missing return value descriptions:
>> make W=2 clean net/iucv/ 2>&1 | grep ^Warning
> Warning: net/iucv/iucv.c:691 No description found for return value of 'iucv_sever_pathid'
> Warning: net/iucv/iucv.c:1099 No description found for return value of 'iucv_message_receive_iprmdata'
> Warning: net/iucv/iucv.c:1856 No description found for return value of 'iucv_init'
> Warning: net/iucv/iucv.c:691 No description found for return value of 'iucv_sever_pathid'
> Warning: net/iucv/iucv.c:1099 No description found for return value of 'iucv_message_receive_iprmdata'
> Warning: net/iucv/iucv.c:1856 No description found for return value of 'iucv_init'
> Warning: net/iucv/af_iucv.c:131 No description found for return value of 'iucv_msg_length'
> Warning: net/iucv/af_iucv.c:150 No description found for return value of 'iucv_sock_in_state'
> Warning: net/iucv/af_iucv.c:163 No description found for return value of 'iucv_below_msglim'
> Warning: net/iucv/af_iucv.c:889 No description found for return value of 'iucv_send_iprm'
> Warning: net/iucv/af_iucv.c:131 No description found for return value of 'iucv_msg_length'
> Warning: net/iucv/af_iucv.c:150 No description found for return value of 'iucv_sock_in_state'
> Warning: net/iucv/af_iucv.c:163 No description found for return value of 'iucv_below_msglim'
> Warning: net/iucv/af_iucv.c:889 No description found for return value of 'iucv_send_iprm'
>
> Our team will fix those, unless you want to add them to this patch.
Please go ahead with those fixes.
Thanks.
--
~Randy
next prev parent reply other threads:[~2026-02-03 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 7:52 [PATCH v3 net-next] net/iucv: clean up iucv kernel-doc warnings Randy Dunlap
2026-02-03 9:39 ` Alexandra Winter
2026-02-03 18:30 ` Randy Dunlap [this message]
2026-02-05 4:40 ` Jakub Kicinski
2026-02-05 4:50 ` 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=2dfeee9a-ea5e-4f8d-822e-d7ee84544c5e@infradead.org \
--to=rdunlap@infradead.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=twinkler@linux.ibm.com \
--cc=wintera@linux.ibm.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