From: patchwork-bot+netdevbpf@kernel.org
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, aconole@redhat.com, echaudro@redhat.com,
i.maximets@ovn.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
dev@openvswitch.org
Subject: Re: [PATCH net-next v5] net: openvswitch: clean up some kernel-doc warnings
Date: Thu, 05 Mar 2026 02:40:37 +0000 [thread overview]
Message-ID: <177267843754.2487871.12321677190144402614.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260304012437.469151-1-rdunlap@infradead.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 3 Mar 2026 17:24:37 -0800 you wrote:
> Fix some kernel-doc warnings in openvswitch.h:
>
> Mark enum placeholders that are not used as "private" so that kernel-doc
> comments are not needed for them.
>
> Correct names for 2 enum values:
> Warning: include/uapi/linux/openvswitch.h:300 Excess enum value
> '@OVS_VPORT_UPCALL_SUCCESS' description in 'ovs_vport_upcall_attr'
> Warning: include/uapi/linux/openvswitch.h:300 Excess enum value
> '@OVS_VPORT_UPCALL_FAIL' description in 'ovs_vport_upcall_attr'
>
> [...]
Here is the summary with links:
- [net-next,v5] net: openvswitch: clean up some kernel-doc warnings
https://git.kernel.org/netdev/net-next/c/39ae83b0f557
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-03-05 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 1:24 [PATCH net-next v5] net: openvswitch: clean up some kernel-doc warnings Randy Dunlap
2026-03-04 21:23 ` Ilya Maximets
2026-03-04 21:32 ` Randy Dunlap
2026-03-05 2:40 ` 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=177267843754.2487871.12321677190144402614.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
/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