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 v12 0/8] add mptcp_subflow bpf_iter
Date: Mon, 21 Oct 2024 19:37:43 +0200 [thread overview]
Message-ID: <e2ef3aec-d42c-4791-aa47-f35be0c6a5dd@kernel.org> (raw)
In-Reply-To: <cover.1729267039.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 18/10/2024 18:00, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> v12:
> - squash patch 4 and patch 6 into one.
> - use TCP_IS_MPTCP instead of TCP_CONGESTION.
Thank you for the new version. The new test looks good to me.
I just applied the series in our tree, before the BPF sched patches.
There were quite a few conflicts I had to resolve, and code to move from
already applied patches, to the new ones here. I also fixed a few issues
reported by checkpatch while at it: __aligned(), s/veriable/variable/,
and go to the new lines for some long lines. Can you please check
everything has been applied as expected?
New patches for t/upstream:
- d5e58ecf7fa8: Squash to "selftests/bpf: Add bpf scheduler test"
- 5a74aa7f2e5e: Revert "bpf: Export more bpf_burst related functions"
- 5ad76db0b5cb: Squash to "bpf: Add bpf_mptcp_sched_kfunc_set"
- 11fcde02a32a: tg:msg: update after the recent squash-to patch
- dae167c2e8d9: conflict in t/mptcp-add-sched_data-helpers-2
- e5a676e5c48d: conflict in t/mptcp-add-bpf_mptcp_sched_ops
- 0f852643d30d: conflict in t/bpf-Add-bpf_mptcp_sched_kfunc_set
- 0bb27f0be108: conflict in t/selftests-bpf-Add-bpf-scheduler-test
- 637c2378c777: conflict in t/selftests-bpf-add-bpf_first-scheduler
- 5ac242f7d4d0: conflict in t/bpf-Export-more-bpf_burst-related-functions
- Results: 096928239c3d..cb54960b2b51 (export)
- d5e58ecf7fa8: "squashed" patch 6/8 in "selftests/bpf: Add bpf
scheduler test"
- 5a74aa7f2e5e: "squashed" patch 7/8 in "bpf: Export more bpf_burst
related functions"
- 5ad76db0b5cb: "squashed" patch 8/8 in "bpf: Add bpf_mptcp_sched_kfunc_set"
- Results: cb54960b2b51..95f1f908edb3 (export)
Tests are now in progress:
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/f2798ec6af402483b2dde42f108c05363fef8706/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-10-21 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 16:00 [PATCH mptcp-next v12 0/8] add mptcp_subflow bpf_iter Geliang Tang
2024-10-18 16:00 ` [PATCH mptcp-next v12 1/8] bpf: Register mptcp common kfunc set Geliang Tang
2024-10-18 16:00 ` [PATCH mptcp-next v12 2/8] bpf: Add mptcp_subflow bpf_iter Geliang Tang
2024-10-18 16:00 ` [PATCH mptcp-next v12 3/8] bpf: Acquire and release mptcp socket Geliang Tang
2024-10-18 16:00 ` [PATCH mptcp-next v12 4/8] selftests/bpf: More endpoints for endpoint_init Geliang Tang
2024-10-18 16:00 ` [PATCH mptcp-next v12 5/8] selftests/bpf: Add mptcp_subflow bpf_iter subtest Geliang Tang
2024-10-18 16:00 ` [PATCH mptcp-next v12 6/8] Squash to "selftests/bpf: Add bpf scheduler test" Geliang Tang
2024-10-18 16:00 ` [PATCH mptcp-next v12 7/8] Revert "bpf: Export more bpf_burst related functions" Geliang Tang
2024-10-18 16:00 ` [PATCH mptcp-next v12 8/8] Squash to "bpf: Add bpf_mptcp_sched_kfunc_set" Geliang Tang
2024-10-18 17:11 ` [PATCH mptcp-next v12 0/8] add mptcp_subflow bpf_iter MPTCP CI
2024-10-21 17:37 ` 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=e2ef3aec-d42c-4791-aa47-f35be0c6a5dd@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