linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v2 net-next] net/iucv: clean up iucv kernel-doc warnings
Date: Mon, 2 Feb 2026 14:07:51 -0800	[thread overview]
Message-ID: <136674a3-cf8d-4da9-a82d-d0edea6aca03@infradead.org> (raw)
In-Reply-To: <2ddf6abd-d10c-4d75-8f84-0fd1ccb5435c@linux.ibm.com>

Hi,

On 2/2/26 7:35 AM, Alexandra Winter wrote:
> 
> 
> On 01.02.26 08:23, Randy Dunlap wrote:
>> Fix numerous (many) kernel-doc warnings in iucv.[ch]:
>>
>> - remove kernel-doc on static functions in iucv.c
>> - convert function documentation comments to a common (kernel-doc) look,
>>   even for static functions (without "/**")
>> - use matching parameter and parameter description names
>>
>> 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>
>> ---
> 
> Thank you very much for your effort Randy.
> FYI: I had to use 'scripts/kernel-doc.py -none -Wall include/net/iucv/*' to see the warnings.
> 
> 
> 
>> v2:
>> - correct verbs in descriptions of 2 functions (Jakub)
>> - removed duplicate kernel-doc comments from the header file (Jakub)
>>
>> Cc: Alexandra Winter <wintera@linux.ibm.com>
>> Cc: Thorsten Winkler <twinkler@linux.ibm.com>
>> Cc: linux-s390@vger.kernel.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: Simon Horman <horms@kernel.org>
>>
>>  include/net/iucv/iucv.h |  209 ------------------------------
>>  net/iucv/iucv.c         |  259 ++++++++++++++++++--------------------
>>  2 files changed, 128 insertions(+), 340 deletions(-)
>>
>> --- linux-next-20260130.orig/include/net/iucv/iucv.h
>> +++ linux-next-20260130/include/net/iucv/iucv.h
>> @@ -70,7 +70,7 @@
>>  #define IUCV_IPLOCAL	0x01
>>  
>>  /*
>> - * iucv_array : Defines buffer array.
>> + * iucv_array - Defines buffer array.
> 
> Did that create a kernel doc warning? It's a struct, not a function.

It's not kernel-doc, so no warning.
However, JFYI, for kernel-doc, it would need a "short description" after the
hyphen, whether it's a function, struct, enum, typedef, union, or define (macro).


> I propose
> + * struct iucv_array
> like other structs in this file.

OK, that's fine for structs that don't have kernel-doc notation.

> [...]
> 
>> @@ -757,13 +742,12 @@ static void iucv_cleanup_queue(void)
>>  }
>>
>>  /**
>> - * iucv_register:
>> + * iucv_register - Registers a driver with IUCV.
>> + *
>>   * @handler: address of iucv handler structure
>>   * @smp: != 0 indicates that the handler can deal with out of order messages
>>   *
>> - * Registers a driver with IUCV.
>> - *
>> - * Returns 0 on success, -ENOMEM if the memory allocation for the pathid
>> + * Returns: 0 on success, -ENOMEM if the memory allocation for the pathid
>>   * table failed, or -EIO if IUCV_DECLARE_BUFFER failed on all cpus.
>>   */
>>  int iucv_register(struct iucv_handler *handler, int smp)
> 
> Before this one, you changed /** to /*
> after this one you left /**
> That's a bit inconsistent.

That's described in the patch description:

>> - remove kernel-doc on static functions in iucv.c

but I can restore the "/**" (i.e., not change them to "/*").
OK, I'll do that.


> 
> All the fixes look good to me. And they get rid of the mentioned warnings.
> I appreciate your approach to use the existing wording, though it may not
> be according to the latest style guidelines.

Is that IBM style guidelines or kernel?

> Reviewed-by: Alexandra Winter <wintera@linux.ibm.com>


I'll send a v3. Hopefully it will be satisfactory.

Thanks.
-- 
~Randy


  reply	other threads:[~2026-02-02 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-01  7:23 [PATCH v2 net-next] net/iucv: clean up iucv kernel-doc warnings Randy Dunlap
2026-02-02 15:35 ` Alexandra Winter
2026-02-02 22:07   ` Randy Dunlap [this message]
2026-02-03  9:39     ` Alexandra Winter
2026-02-06  7:01   ` 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=136674a3-cf8d-4da9-a82d-d0edea6aca03@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;
as well as URLs for NNTP newsgroup(s).