From: Matthieu Baerts <matttbe@kernel.org>
To: mptcp@lists.linux.dev, Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v3 00/15] refactor PM interfaces
Date: Thu, 10 Oct 2024 10:22:28 +0200 [thread overview]
Message-ID: <1da2a366-63c5-454a-9455-30b7fdb4ac21@kernel.org> (raw)
In-Reply-To: <bb0bd72b-cb68-0386-b7c5-76383707840b@gmail.com>
Hi Geliang,
On 10/10/2024 08:52, MPTCP CI wrote:
> Hi Geliang,
>
> Thank you for your modifications, that's great!
>
> Our CI did some validations and here is its report:
>
> - KVM Validation: normal: Unstable: 1 failed test(s): packetdrill_dss 🔴
> - KVM Validation: debug: Unstable: 1 failed test(s): packetdrill_dss 🔴
That's interesting: the CI had this error, because the code doesn't have
"mptcp: fallback when MPTCP opts are dropped after 1st data" commit.
https://github.com/multipath-tcp/mptcp_net-next/commits/8a88c16c3a19
That's appently because when using the "Based-on", Patchew will use the
tag it created, then apply the new patches. It will then not use the
last version of the "export" branch, then apply the dependences, then
the new ones.
In other words, we can ignore the failed tests here.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-10-10 8:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 5:47 [PATCH mptcp-next v3 00/15] refactor PM interfaces Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 01/15] mptcp: add id parameter for get_addr Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 02/15] mptcp: add addr " Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 03/15] mptcp: reuse sending nlmsg code in get_addr Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 04/15] mptcp: change info of get_addr as const Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 05/15] mptcp: refactor dump_addr with id bitmap Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 06/15] mptcp: refactor dump_addr with get_addr Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 07/15] mptcp: reuse sending nlmsg code in dump_addr Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 08/15] mptcp: add loc and rem for set_flags Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 09/15] mptcp: update address type of get_local_id Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 10/15] mptcp: change is_backup interfaces as get_flags Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 11/15] mptcp: hold pm lock when deleting entry Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 12/15] mptcp: rename mptcp_pm_remove_addrs Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 13/15] mptcp: drop free_list for deleting entries Geliang Tang
2024-10-10 5:47 ` [PATCH mptcp-next v3 14/15] mptcp: drop struct mptcp_pm_local Geliang Tang
2024-10-10 5:48 ` [PATCH mptcp-next v3 15/15] mptcp: drop struct mptcp_pm_add_entry Geliang Tang
2024-10-10 6:52 ` [PATCH mptcp-next v3 00/15] refactor PM interfaces MPTCP CI
2024-10-10 8:22 ` Matthieu Baerts [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=1da2a366-63c5-454a-9455-30b7fdb4ac21@kernel.org \
--to=matttbe@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;
as well as URLs for NNTP newsgroup(s).