MPTCP Archive mirror
 help / color / mirror / Atom feed
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 v9 0/4] setsockopt per subflow: BPF
Date: Mon, 29 Apr 2024 20:38:59 +0200	[thread overview]
Message-ID: <7a8b5e60-d42c-4ed4-a8df-a1a9abf5fddd@kernel.org> (raw)
In-Reply-To: <cover.1713920939.git.tanggeliang@kylinos.cn>

Hi Geliang, Mat,

On 24/04/2024 03:13, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
> 
> v9:
>  - validate the return value of snprintf in patch 2 as Mat suggested.
>  - patch 2 depends on "selftests/bpf: Add RUN_MPTCP_TEST macro", so this
>    series could be merged in this order:
>    1 selftests/bpf: Add mptcp subflow example
>    2 selftests/bpf: Add RUN_MPTCP_TEST macro
>    3 selftests/bpf: Add mptcp subflow subtest
>    4 selftests/bpf: Handle SIGINT when creating netns

Thank you for the v9, and for the reviews!

New patches for t/upstream:
- fbbcd761fba3: selftests/bpf: Add mptcp subflow example
- Results: a11773e3c938..97e0136c8e33 (export)

New patches for t/upstream:
- 9961ad9244d7: selftests/bpf: Add mptcp subflow subtest
- 2f83b94e9407: selftests/bpf: Handle SIGINT when creating netns
- 84add332488a: conflict in t/selftests-bpf-Add-bpf-scheduler-test
- bdc876b898a8: conflict in t/selftests-bpf-add-bpf_first-scheduler
- Results: 97e0136c8e33..d3dcecbbf741 (export)

- d7b5a88080f9: "squashed" in "selftests/bpf: Add bpf scheduler test"
- 774ca6584944: Squash to "selftests/bpf: Add bpf scheduler test"
  (removed unused variable)
- Results: d3dcecbbf741..4e475b683f9a (export)

Tests are now in progress:

- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/de55140562593e303216dad6fd1e925cd618164d/checks

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


      parent reply	other threads:[~2024-04-29 18:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24  1:13 [PATCH mptcp-next v9 0/4] setsockopt per subflow: BPF Geliang Tang
2024-04-24  1:13 ` [PATCH mptcp-next v9 1/4] selftests/bpf: Add mptcp subflow example Geliang Tang
2024-04-24  1:13 ` [PATCH mptcp-next v9 2/4] selftests/bpf: Add mptcp subflow subtest Geliang Tang
2024-04-24  1:13 ` [PATCH mptcp-next v9 3/4] selftests/bpf: Handle SIGINT when creating netns Geliang Tang
2024-04-24  1:13 ` [PATCH mptcp-next v9 4/4] Squash to "selftests/bpf: Add bpf scheduler test" Geliang Tang
2024-04-24  2:33 ` [PATCH mptcp-next v9 0/4] setsockopt per subflow: BPF MPTCP CI
2024-04-24 15:37 ` Mat Martineau
2024-04-29 18:38 ` 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=7a8b5e60-d42c-4ed4-a8df-a1a9abf5fddd@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).