From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, dsahern@kernel.org
Subject: Re: [PATCH iproute2 0/2] use get_task_name in ss
Date: Thu, 22 Oct 2026 18:30:07 +0000 [thread overview]
Message-ID: <179269380756.87273.3721149238282164503.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261021160020.3838946-1-stephen@networkplumber.org>
Hello:
This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Wed, 21 Oct 2026 08:57:21 -0700 you wrote:
> Recent proposed patch by Prashanth showed that ss command parsing of
> proc with fscanf is fragile. Here is a pair of patches which allows
> reusing existing code in iproute2 lib/fs for that instead.
>
> Stephen Hemminger (2):
> lib: add root path argument to get_task_name
> ss: use get_task_name instead of parsing stat
>
> [...]
Here is the summary with links:
- [iproute2,1/2] lib: add root path argument to get_task_name
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=c92418663848
- [iproute2,2/2] ss: use get_task_name instead of parsing stat
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=89d08bac1661
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-10-22 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 15:57 [PATCH iproute2 0/2] use get_task_name in ss Stephen Hemminger
2026-10-21 15:57 ` [PATCH iproute2 1/2] lib: add root path argument to get_task_name Stephen Hemminger
2026-10-21 15:57 ` [PATCH iproute2 2/2] ss: use get_task_name instead of parsing stat Stephen Hemminger
2026-10-22 18:30 ` 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=179269380756.87273.3721149238282164503.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@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