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 0/2] Drop mptcp_pm_subflow_chk_stale in bpf
Date: Fri, 7 Aug 2026 13:46:02 +0200 [thread overview]
Message-ID: <d80ad28c-afb9-4bcd-a5ea-a04b496e90ff@kernel.org> (raw)
In-Reply-To: <cover.1786007209.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 06/08/2026 11:10, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> Since mptcp_pm_subflow_chk_stale is removed in the "mptcp: address stall
> under memory pressure" series, this patch drops it from BPF to keep the
> BPF tests passing.
Thank you for fixing that!
New patches for t/upstream:
- 3e3fab142e29: "squashed" patch 1/2 in "bpf: Export mptcp packet scheduler helpers"
- b1602f423178: "squashed" patch 2/2 in "selftests/bpf: Add bpf_burst scheduler & test"
- Results: 7bf94a8339a9..b67053e5e63b (export)
Tests are now in progress:
- export: https://github.com/multipath-tcp/mptcp_net-next/commit/58dcc35549b1dfcf3d689fc5e163a25fb11a335c/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-08-07 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 9:10 [PATCH mptcp-next 0/2] Drop mptcp_pm_subflow_chk_stale in bpf Geliang Tang
2026-08-06 9:10 ` [PATCH mptcp-next 1/2] Squash to "bpf: Export mptcp packet scheduler helpers" Geliang Tang
2026-08-06 9:10 ` [PATCH mptcp-next 2/2] Squash to "selftests/bpf: Add bpf_burst scheduler & test" Geliang Tang
2026-08-06 10:17 ` [PATCH mptcp-next 0/2] Drop mptcp_pm_subflow_chk_stale in bpf MPTCP CI
2026-08-06 16:54 ` Paolo Abeni
2026-08-07 11:46 ` 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=d80ad28c-afb9-4bcd-a5ea-a04b496e90ff@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