From: Matthieu Baerts <matttbe@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org, mptcp@lists.linux.dev
Subject: Re: [PATCH iproute2 1/2] mptcp: monitor: also show iface name
Date: Thu, 19 Feb 2026 20:26:05 +0100 [thread overview]
Message-ID: <0248ef7e-0274-46d6-94aa-b3725e29e52f@kernel.org> (raw)
In-Reply-To: <20260219112220.6576b50d@phoenix.local>
On 19/02/2026 20:22, Stephen Hemminger wrote:
> On Thu, 19 Feb 2026 18:38:51 +0100
> Matthieu Baerts <matttbe@kernel.org> wrote:
>
>>>>> Please fix the whole function.
>>>>
>>>> Doing that would likely break scripts parsing 'ip mptcp monitor' output,
>>>> are you sure we should still change this output format?
>>>
>>> I doubt scripts are parsing this weird format. That is one more reason for JSON
>>
>> Not as weird as 'ss -i' format where there are even more scripts parsing
>> that :)
>
> Agreed ss is a RFM.
> I did take a shot at doing JSON there (with some help from Claude), just haven't gotten back to it.
That would be great to have! Thank you for having started!
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-02-19 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 12:03 [PATCH iproute2 0/2] mptcp: support colors & display iface name Matthieu Baerts (NGI0)
2026-02-11 12:03 ` [PATCH iproute2 1/2] mptcp: monitor: also show " Matthieu Baerts (NGI0)
2026-02-18 18:31 ` Stephen Hemminger
2026-02-18 19:03 ` Matthieu Baerts
2026-02-19 17:11 ` Stephen Hemminger
2026-02-19 17:38 ` Matthieu Baerts
2026-02-19 19:22 ` Stephen Hemminger
2026-02-19 19:26 ` Matthieu Baerts [this message]
2026-02-11 12:03 ` [PATCH iproute2 2/2] mptcp: display addr & ifname in color Matthieu Baerts (NGI0)
2026-02-18 4:00 ` [PATCH iproute2 0/2] mptcp: support colors & display iface name patchwork-bot+netdevbpf
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=0248ef7e-0274-46d6-94aa-b3725e29e52f@kernel.org \
--to=matttbe@kernel.org \
--cc=dsahern@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox