From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next 0/7] man page corrections
Date: Sat, 31 Jan 2026 19:20:15 +0000 [thread overview]
Message-ID: <176988721535.4169653.15303349092721217252.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260124195824.221305-1-stephen@networkplumber.org>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Sat, 24 Jan 2026 11:49:24 -0800 you wrote:
> AI does a great job of finding and fixing manual pages.
> This patch series is the result of editorial review and correction of
> subsystem man pages, addressing grammatical errors, style inconsistencies, and
> clarity issues throughout the documentation.
>
> The corrections cover the following subsystems:
> - DCB (Data Center Bridging)
> - devlink
> - Statistics tools (lnstat, rtacct, nstat)
> - netshaper
> - TIPC
> - vdpa
> - RDMA
>
> [...]
Here is the summary with links:
- [iproute2-next,1/7] dcb: fix grammar and style issues in man pages
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=9be6919137c5
- [iproute2-next,2/7] devlink: fix grammar and style issues in man pages
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=aea0ff56598c
- [iproute2-next,3/7] fix grammar and style issues in man pages for stat related pages
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=7bfb82531d36
- [iproute2-next,4/7] netshaper: fix grammar and style issues in man page
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=8a966d9025ed
- [iproute2-next,5/7] tipc: fix grammar and style issues in man pages
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=df638236f887
- [iproute2-next,6/7] vdpa: fix grammar, titles, and formatting in man pages
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=4706396c3179
- [iproute2-next,7/7] rdma: fix grammar, formatting, and style in man pages
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=4d4e73273a45
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-01-31 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 19:49 [PATCH iproute2-next 0/7] man page corrections Stephen Hemminger
2026-01-24 19:49 ` [PATCH iproute2-next 1/7] dcb: fix grammar and style issues in man pages Stephen Hemminger
2026-01-24 19:49 ` [PATCH iproute2-next 2/7] devlink: " Stephen Hemminger
2026-01-24 19:49 ` [PATCH iproute2-next 3/7] fix grammar and style issues in man pages for stat related pages Stephen Hemminger
2026-01-24 19:49 ` [PATCH iproute2-next 4/7] netshaper: fix grammar and style issues in man page Stephen Hemminger
2026-01-24 19:49 ` [PATCH iproute2-next 5/7] tipc: fix grammar and style issues in man pages Stephen Hemminger
2026-01-24 19:49 ` [PATCH iproute2-next 6/7] vdpa: fix grammar, titles, and formatting " Stephen Hemminger
2026-01-24 19:49 ` [PATCH iproute2-next 7/7] rdma: fix grammar, formatting, and style " Stephen Hemminger
2026-01-31 19: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=176988721535.4169653.15303349092721217252.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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