From: patchwork-bot+netdevbpf@kernel.org
To: Alexandra Winter <wintera@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch,
twinkler@linux.ibm.com, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, aswin@linux.ibm.com,
hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
borntraeger@linux.ibm.com, svens@linux.ibm.com, horms@kernel.org,
nagamani@linux.ibm.com
Subject: Re: [PATCH net-next] net/iucv: Add missing kernel-doc return value descriptions
Date: Wed, 01 Apr 2026 03:20:11 +0000 [thread overview]
Message-ID: <177501361178.3053582.15867964661733976035.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260330114436.2010108-1-wintera@linux.ibm.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Mar 2026 13:44:36 +0200 you wrote:
> From: Nagamani PV <nagamani@linux.ibm.com>
>
> Add missing return value descriptions for several functions in
> net/iucv/af_iucv.c and net/iucv/iucv.c to address kernel-doc warnings.
>
> Warnings detected with:
> scripts/kernel-doc -none -Wall net/iucv/*
> 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'
> ...
>
> [...]
Here is the summary with links:
- [net-next] net/iucv: Add missing kernel-doc return value descriptions
https://git.kernel.org/netdev/net-next/c/f1359c240191
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-01 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 11:44 [PATCH net-next] net/iucv: Add missing kernel-doc return value descriptions Alexandra Winter
2026-04-01 3:20 ` patchwork-bot+netdevbpf [this message]
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=177501361178.3053582.15867964661733976035.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=andrew+netdev@lunn.ch \
--cc=aswin@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nagamani@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=svens@linux.ibm.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