All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: stephen@networkplumber.org, dsahern@gmail.com,
	netdev@vger.kernel.org, mptcp@lists.linux.dev,
	martineau@kernel.org, geliang@kernel.org, dcaratti@redhat.com
Subject: Re: [PATCH iproute2-net] ss: mptcp: subflow: display seq counters as decimal
Date: Mon, 10 Mar 2025 16:20:33 +0000	[thread overview]
Message-ID: <174162363352.3590516.2874190652040692999.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250226-iproute2-net-ss-ulp-mptcp-dec-v1-1-4f4177cff217@kernel.org>

Hello:

This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:

On Wed, 26 Feb 2025 12:08:44 +0100 you wrote:
> This is similar to commit cfa70237 ("ss: mptcp: display seq related
> counters as decimal") but for the subflow info this time. This is also
> aligned with what is printed for TCP sockets.
> 
> That looks better to do the same with the subflow info (ss -ti), to
> compare with the MPTCP info (ss -Mi), or for those who want to easily
> count how many bytes have been exchanged between two runs without having
> to think in hexa.
> 
> [...]

Here is the summary with links:
  - [iproute2-net] ss: mptcp: subflow: display seq counters as decimal
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=e3f9681d4a77

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-03-10 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 11:08 [PATCH iproute2-net] ss: mptcp: subflow: display seq counters as decimal Matthieu Baerts (NGI0)
2025-03-10 16: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=174162363352.3590516.2874190652040692999.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dcaratti@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=geliang@kernel.org \
    --cc=martineau@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.