From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] ss: fix grammar, articles, and phrasing in man page
Date: Sat, 31 Jan 2026 19:20:16 +0000 [thread overview]
Message-ID: <176988721660.4169653.8292887643483830988.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260124200107.222116-1-stephen@networkplumber.org>
Hello:
This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Sat, 24 Jan 2026 12:00:41 -0800 you wrote:
> This patch addresses grammatical errors, awkward phrasing, missing
> articles, and singular/plural agreement issues throughout the ss
> man page documentation.
>
> Main corrections:
>
> Grammar and agreement (10 instances):
> - Fix singular/plural: "connection" -> "connections"
> - Fix "five kind" -> "five kinds"
> - Fix "packet" -> "packets" (7 instances throughout memory descriptions)
> - Fix "the retransmission occurred" -> "retransmissions have occurred"
> - Fix "process using socket" -> "processes using sockets"
> - Fix "thread using socket" -> "threads using sockets"
> - Fix "socket option" -> "socket options"
>
> [...]
Here is the summary with links:
- [iproute2-next] ss: fix grammar, articles, and phrasing in man page
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=cd01762163b7
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: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 20:00 [PATCH iproute2-next] ss: fix grammar, articles, and phrasing in man page Stephen Hemminger
2026-01-26 16:53 ` Simon Horman
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=176988721660.4169653.8292887643483830988.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