From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute 1/2] json_writer: support control character escaping
Date: Mon, 13 Apr 2026 19:10:06 +0000 [thread overview]
Message-ID: <177610740680.501842.5837972274983153432.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260410224745.93416-1-stephen@networkplumber.org>
Hello:
This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Fri, 10 Apr 2026 15:47:44 -0700 you wrote:
> Iproute2 never handled control characters in strings correctly.
> There are some cases like where string is under user control
> like paths in ss command. Make iproute2 json output conform
> to RFC 8259.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> [...]
Here is the summary with links:
- [iproute,1/2] json_writer: support control character escaping
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=9e99260759b7
- [iproute,2/2] json_writer: fix builtin test code
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=fe811be6564c
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-04-13 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 22:47 [PATCH iproute 1/2] json_writer: support control character escaping Stephen Hemminger
2026-04-10 22:47 ` [PATCH iproute 2/2] json_writer: fix builtin test code Stephen Hemminger
2026-04-13 19:10 ` 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=177610740680.501842.5837972274983153432.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