From: patchwork-bot+netdevbpf@kernel.org
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
linux-wireless@vger.kernel.org, linux-wpan@vger.kernel.org,
j.vosburgh@gmail.com, andy@greyhouse.net,
johannes@sipsolutions.net, mchehab@kernel.org,
alex.aring@gmail.com, stefan@datenfreihafen.org,
miquel.raynal@bootlin.com, marcel@holtmann.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us,
dave.taht@bufferbloat.net, moshe@mellanox.com,
jacob.e.keller@intel.com, razor@blackwall.org,
benjamin.berg@intel.com, jbenc@redhat.com, lesliemonis@gmail.com,
tahiliani@nitk.edu.in, gautamramk@gmail.com,
prameela.j04cs@gmail.com, siva.rebbagondla@redpinesignals.com,
kvalo@kernel.org
Subject: Re: [PATCH v2 net 0/9] net: fix kernel-doc problems in include/net/
Date: Sat, 15 Jul 2023 03:50:22 +0000 [thread overview]
Message-ID: <168939302206.24345.17268044128458529302.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230714045127.18752-1-rdunlap@infradead.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 13 Jul 2023 21:51:18 -0700 you wrote:
> Fix many (but not all) kernel-doc warnings in include/net/.
>
> [PATCH v2 net 1/9] net: bonding: remove kernel-doc comment marker
> [PATCH v2 net 2/9] net: cfg802154: fix kernel-doc notation warnings
> [PATCH v2 net 3/9] codel: fix kernel-doc notation warnings
> [PATCH v2 net 4/9] devlink: fix kernel-doc notation warnings
> [PATCH v2 net 5/9] inet: frags: remove kernel-doc comment marker
> [PATCH v2 net 6/9] net: llc: fix kernel-doc notation warnings
> [PATCH v2 net 7/9] net: NSH: fix kernel-doc notation warning
> [PATCH v2 net 8/9] pie: fix kernel-doc notation warning
> [PATCH v2 net 9/9] rsi: remove kernel-doc comment marker
>
> [...]
Here is the summary with links:
- [v2,net,1/9] net: bonding: remove kernel-doc comment marker
https://git.kernel.org/netdev/net/c/a66557c79020
- [v2,net,2/9] net: cfg802154: fix kernel-doc notation warnings
https://git.kernel.org/netdev/net/c/a63e40444e1b
- [v2,net,3/9] codel: fix kernel-doc notation warnings
https://git.kernel.org/netdev/net/c/cfe57122bba5
- [v2,net,4/9] devlink: fix kernel-doc notation warnings
https://git.kernel.org/netdev/net/c/839f55c5ebdf
- [v2,net,5/9] inet: frags: eliminate kernel-doc warning
https://git.kernel.org/netdev/net/c/d20909a0689f
- [v2,net,6/9] net: llc: fix kernel-doc notation warnings
https://git.kernel.org/netdev/net/c/201a08830d8c
- [v2,net,7/9] net: NSH: fix kernel-doc notation warning
https://git.kernel.org/netdev/net/c/d1533d726aa1
- [v2,net,8/9] pie: fix kernel-doc notation warning
https://git.kernel.org/netdev/net/c/d1cca974548d
- [v2,net,9/9] rsi: remove kernel-doc comment marker
https://git.kernel.org/netdev/net/c/04be3c95da82
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:[~2023-07-15 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 4:51 [PATCH v2 net 0/9] net: fix kernel-doc problems in include/net/ Randy Dunlap
2023-07-15 3:50 ` 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=168939302206.24345.17268044128458529302.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alex.aring@gmail.com \
--cc=andy@greyhouse.net \
--cc=benjamin.berg@intel.com \
--cc=dave.taht@bufferbloat.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gautamramk@gmail.com \
--cc=j.vosburgh@gmail.com \
--cc=jacob.e.keller@intel.com \
--cc=jbenc@redhat.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=lesliemonis@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mchehab@kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prameela.j04cs@gmail.com \
--cc=razor@blackwall.org \
--cc=rdunlap@infradead.org \
--cc=siva.rebbagondla@redpinesignals.com \
--cc=stefan@datenfreihafen.org \
--cc=tahiliani@nitk.edu.in \
--cc=xiyou.wangcong@gmail.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).