MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v3 1/2] selftests: mptcp: join: add ss mptcp support check
Date: Mon, 19 Feb 2024 11:43:12 +0100	[thread overview]
Message-ID: <63ba5d51-ae55-4c71-84c5-0d4610a955c9@kernel.org> (raw)
In-Reply-To: <e90ec1eb-16d7-46ee-9835-d93fdbad6702@kernel.org>

Hi Geliang,

On 19/02/2024 09:52, Matthieu Baerts wrote:
> Hi Geliang,
> 
> On 19/02/2024 09:22, Geliang Tang wrote:
>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>
>> Commands 'ss -M' are used in script mptcp_join.sh to display only MPTCP
>> sockets. So it must be checked if ss tool supports MPTCP in this script.
> 
> Thank you for the update, I will queue it for -net, with:
> 
> Fixes: e274f7154008 ("selftests: mptcp: add subflow limits test-cases")
> Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>

Just did:

New patches for t/upstream-net and t/upstream:
- ee636468e74e: selftests: mptcp: join: add ss mptcp support check
- Results: 22c802d10725..43a48b2f8697 (export-net)
- 05d22fbbbb38: conflict in t/selftests-mptcp-stop-forcing-iptables-legacy
- Results: d5aedc5b25ce..1642cc21aa85 (export)

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.

  reply	other threads:[~2024-02-19 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  8:22 [PATCH mptcp-next v3 0/2] add helpers and vars in mptcp_lib.sh, part 1 Geliang Tang
2024-02-19  8:22 ` [PATCH mptcp-next v3 1/2] selftests: mptcp: join: add ss mptcp support check Geliang Tang
2024-02-19  8:52   ` Matthieu Baerts
2024-02-19 10:43     ` Matthieu Baerts [this message]
2024-02-19  8:22 ` [PATCH mptcp-next v3 2/2] selftests: mptcp: add mptcp_lib_check_tools helper Geliang Tang
2024-02-19  9:01   ` Matthieu Baerts
2024-02-19  9:17   ` selftests: mptcp: add mptcp_lib_check_tools helper: Tests Results MPTCP CI
2024-02-19  9:47   ` MPTCP CI

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=63ba5d51-ae55-4c71-84c5-0d4610a955c9@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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