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 v6 0/2] patches for new MPTCP subflow subtest
Date: Wed, 15 May 2024 18:53:33 +0200	[thread overview]
Message-ID: <f8beab88-25b2-48ce-8d94-b3d468aeb2de@kernel.org> (raw)
In-Reply-To: <cover.1715769419.git.tanggeliang@kylinos.cn>

Hi Geliang,

On 15/05/2024 12:38, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
> 
> v6:
>  - fix CI errors.
>  - rebased.
Thank you for the new version!

Now in our tree (feat. for other trees)

New patches for t/upstream:
- 998f0e3afd37: selftests/bpf: Add mptcp pm_nl_ctl link
- 4de3c65cee0e: conflict in t/selftests-bpf-add-bpf_first-scheduler
- a8623b952f92: "squashed" in "selftests/bpf: Add mptcp subflow subtest"
- Results: 767563eb7a1b..f2eb0deee073 (export)

Tests are now in progress:

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

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


      parent reply	other threads:[~2024-05-15 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 10:38 [PATCH mptcp-next v6 0/2] patches for new MPTCP subflow subtest Geliang Tang
2024-05-15 10:38 ` [PATCH mptcp-next v6 1/2] selftests/bpf: Add mptcp pm_nl_ctl link Geliang Tang
2024-05-15 10:38 ` [PATCH mptcp-next v6 2/2] Squash to "selftests/bpf: Add mptcp subflow subtest" Geliang Tang
2024-05-15 11:30 ` [PATCH mptcp-next v6 0/2] patches for new MPTCP subflow subtest MPTCP CI
2024-05-15 16:53 ` 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=f8beab88-25b2-48ce-8d94-b3d468aeb2de@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).