MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>,
	mptcp@lists.linux.dev, Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v9 0/7] add mptcp_subflow bpf_iter
Date: Tue, 15 Oct 2024 13:07:01 +0200	[thread overview]
Message-ID: <33c9b4af-be2b-4991-91a2-4219d591cace@kernel.org> (raw)
In-Reply-To: <c869bcb2-121d-49dc-9da4-199ad8f8a692@kernel.org>

On 15/10/2024 12:59, Matthieu Baerts wrote:
> On 15/10/2024 11:20, Geliang Tang wrote:

(...)

>> The whole order is (from bottom to top):
>>
>> selftests/bpf: Add bpf scheduler test
>> bpf: Add bpf_mptcp_sched_kfunc_set
>> bpf: Add bpf_mptcp_sched_ops
>> mptcp: add sched_data helpers
>> selftests/bpf: Add mptcp_subflow bpf_iter subtest
>> Squash to "selftests/bpf: Add bpf scheduler test"
>> selftests/bpf: More endpoints for endpoint_init
>> selftests/bpf: Add mptcp_subflow bpf_iter test prog
>> bpf: Add mptcp_sock acquire and release helpers
>> bpf: Add mptcp_subflow bpf_iter
>> bpf: Register mptcp common kfunc set
>> selftests/bpf: Add mptcp subflow subtest
>> selftests/bpf: Add getsockopt to inspect mptcp subflow
>> selftests/bpf: Add mptcp subflow example
> 
> Thanks, that's clearer!

I just noticed Daniel sent a pull request to include bpf-net/next into
net-next: it means the 3 last patches from your list will be dropped
from our tree. In this case, I don't have to re-order commit, and simply
apply this series before "mptcp: add sched_data helpers".

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


  reply	other threads:[~2024-10-15 11:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  9:45 [PATCH mptcp-next v9 0/7] add mptcp_subflow bpf_iter Geliang Tang
2024-10-09  9:45 ` [PATCH mptcp-next v9 1/7] bpf: Register mptcp common kfunc set Geliang Tang
2024-10-09  9:45 ` [PATCH mptcp-next v9 2/7] bpf: Add mptcp_subflow bpf_iter Geliang Tang
2024-10-09  9:45 ` [PATCH mptcp-next v9 3/7] bpf: Add mptcp_sock acquire and release helpers Geliang Tang
2024-10-09  9:45 ` [PATCH mptcp-next v9 4/7] selftests/bpf: Add mptcp_subflow bpf_iter test prog Geliang Tang
2024-10-14 16:06   ` Matthieu Baerts
2024-10-15  7:59     ` Geliang Tang
2024-10-15 10:47       ` Matthieu Baerts
2024-10-18  1:22         ` Geliang Tang
2024-10-18 10:56           ` Matthieu Baerts
2024-10-09  9:45 ` [PATCH mptcp-next v9 5/7] selftests/bpf: More endpoints for endpoint_init Geliang Tang
2024-10-09  9:45 ` [PATCH mptcp-next v9 6/7] Squash to "selftests/bpf: Add bpf scheduler test" Geliang Tang
2024-10-09  9:45 ` [PATCH mptcp-next v9 7/7] selftests/bpf: Add mptcp_subflow bpf_iter subtest Geliang Tang
2024-10-09 10:05 ` [PATCH mptcp-next v9 0/7] add mptcp_subflow bpf_iter MPTCP CI
2024-10-14 16:08   ` Matthieu Baerts
2024-10-15  7:27     ` Geliang Tang
2024-10-15  9:01       ` Matthieu Baerts
2024-10-15  9:20         ` Geliang Tang
2024-10-15 10:59           ` Matthieu Baerts
2024-10-15 11:07             ` Matthieu Baerts [this message]
2024-10-18  1:35             ` Geliang Tang
2024-10-15  9:38         ` Geliang Tang
2024-10-15 11:10           ` Matthieu Baerts
2024-10-09 10:54 ` MPTCP CI
2024-10-11 22:27 ` Mat Martineau

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=33c9b4af-be2b-4991-91a2-4219d591cace@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