From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: stephen@networkplumber.org, dsahern@kernel.org,
netdev@vger.kernel.org, mptcp@lists.linux.dev
Subject: Re: [PATCH iproute2-next v2 0/3] ip mptcp monitor: add JSON support
Date: Wed, 25 Feb 2026 16:30:08 +0000 [thread overview]
Message-ID: <177203700829.400635.9348490829138373346.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260223-ipr-monitor-json-v2-0-f91fccccf917@kernel.org>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Mon, 23 Feb 2026 16:28:37 +0100 you wrote:
> With this series, the command 'ip [-t[s]] mptcp monitor' produces an
> output with the JSON format.
>
> - Patch 1: a small refactoring to uniform the code.
>
> - Patch 2: add JSON support in print_timestamp() helper.
>
> [...]
Here is the summary with links:
- [iproute2-next,v2,1/3] mptcp: uniform stream closure
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=fa0217870a8b
- [iproute2-next,v2,2/3] utils: timestamp: add JSON support
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=1fea8c6f3d9b
- [iproute2-next,v2,3/3] mptcp: monitor: add JSON support
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=d37b3aed28c0
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-02-25 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 15:28 [PATCH iproute2-next v2 0/3] ip mptcp monitor: add JSON support Matthieu Baerts (NGI0)
2026-02-23 15:28 ` [PATCH iproute2-next v2 1/3] mptcp: uniform stream closure Matthieu Baerts (NGI0)
2026-02-23 15:28 ` [PATCH iproute2-next v2 2/3] utils: timestamp: add JSON support Matthieu Baerts (NGI0)
2026-02-23 15:28 ` [PATCH iproute2-next v2 3/3] mptcp: monitor: " Matthieu Baerts (NGI0)
2026-02-25 16: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=177203700829.400635.9348490829138373346.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.