From: Matthieu Baerts <matttbe@kernel.org>
To: mptcp@lists.linux.dev
Cc: YonglongLi <liyonglong@chinatelecom.cn>
Subject: Re: [PATCH mptcp-next v2] mptcp: increment RmAddr MIB counter once per RM_ADDR
Date: Mon, 27 May 2024 19:24:42 +0200 [thread overview]
Message-ID: <6318c047-659b-41ae-b375-3d06f9ee46be@kernel.org> (raw)
In-Reply-To: <5d5a8e06-6123-4d42-b615-2a946cdd93e2@gmail.com>
Hello,
On 27/05/2024 18:49, MPTCP CI wrote:
> Hi YonglongLi,
>
> Thank you for your modifications, that's great!
>
> Our CI did some validations and here is its report:
>
> - KVM Validation: normal: Success! ✅
> - KVM Validation: debug: Unstable: 1 failed test(s): packetdrill_sockopts 🔴
Should be fixed by this PR:
https://github.com/multipath-tcp/packetdrill/pull/146
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-05-27 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 16:03 [PATCH mptcp-next v2] mptcp: increment RmAddr MIB counter once per RM_ADDR Matthieu Baerts (NGI0)
2024-05-27 16:49 ` MPTCP CI
2024-05-27 17:24 ` Matthieu Baerts [this message]
2024-06-03 15:51 ` Matthieu Baerts
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=6318c047-659b-41ae-b375-3d06f9ee46be@kernel.org \
--to=matttbe@kernel.org \
--cc=liyonglong@chinatelecom.cn \
--cc=mptcp@lists.linux.dev \
/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