All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v2 0/7] for bpf-next
Date: Thu, 19 May 2022 16:12:14 +0200	[thread overview]
Message-ID: <025be707-a620-8e83-3aca-d962c5ff7ff4@tessares.net> (raw)
In-Reply-To: <cover.1652948238.git.geliang.tang@suse.com>

Hi Geliang,

On 19/05/2022 10:25, Geliang Tang wrote:
> v2:
>  - The series is for bpf-next v5.
>  - patch 1, keep bpf_mptcp_sock_from_subflow() in bpf.c
>  - patch 3, Drop the 'msg' parameter of verify_sk
>  - base-commit: df896c77f02a ("DO-NOT-MERGE: git markup: features
> net-next-next"), export/20220517T155019
>  - The last squash-to patch is for "BPF packet scheduler" series.

I just imported this new series in our tree.

- 7046a98c4501: "squashed" patch 1/7 in "bpf: add
bpf_skc_to_mptcp_sock_proto"
- dc043d25d647: "squashed" patch 2/7 in "selftests/bpf: Enable
CONFIG_IKCONFIG_PROC in config"
- bd3e6e2ffc15: "squashed" patch 3/7 in "selftests/bpf: add MPTCP test base"
- efa55efc427c: "squashed" patch 4/7 in "selftests/bpf: test
bpf_skc_to_mptcp_sock"
- f087e13912ad: "squashed" patch 5/7 in "selftests/bpf: verify token of
struct mptcp_sock"
- 21c0f634b797: "squashed" patch 6/7 in "selftests/bpf: verify ca_name
of struct mptcp_sock"
- d38ab51eb84e: "squashed" patch 7/7 in "selftests/bpf: verify first of
struct mptcp_sock"
- c79872213ec4: conflict in t/selftests-bpf-add-bpf_first-test
- Results: 9ceda99ef71f..5fbf0e7a331f (export)

- 4353cb87928e: "squashed" in "selftests/bpf: add bpf_first test"
- Results: 5fbf0e7a331f..086d4a4a0f34 (export)

Builds and tests are now in progress:



https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20220519T141104

https://github.com/multipath-tcp/mptcp_net-next/actions/workflows/build-validation.yml?query=branch:export

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

      parent reply	other threads:[~2022-05-19 14:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  8:25 [PATCH mptcp-next v2 0/7] for bpf-next Geliang Tang
2022-05-19  8:25 ` [PATCH mptcp-next v2 1/7] bpf: add bpf_skc_to_mptcp_sock_proto Geliang Tang
2022-05-19  8:25 ` [PATCH mptcp-next v2 2/7] selftests/bpf: Enable CONFIG_IKCONFIG_PROC in config Geliang Tang
2022-05-19  8:25 ` [PATCH mptcp-next v2 3/7] selftests/bpf: add MPTCP test base Geliang Tang
2022-05-19  8:25 ` [PATCH mptcp-next v2 4/7] selftests/bpf: test bpf_skc_to_mptcp_sock Geliang Tang
2022-05-19  8:25 ` [PATCH mptcp-next v2 5/7] selftests/bpf: verify token of struct mptcp_sock Geliang Tang
2022-05-19  8:25 ` [PATCH mptcp-next v2 6/7] selftests/bpf: verify ca_name " Geliang Tang
2022-05-19  8:25 ` [PATCH mptcp-next v2 7/7] selftests/bpf: verify first " Geliang Tang
2022-05-19  8:25 ` [PATCH mptcp-next v2] Squash to "selftests/bpf: add bpf_first test" Geliang Tang
2022-05-19 10:49   ` Squash to "selftests/bpf: add bpf_first test": Tests Results MPTCP CI
2022-05-19 14:12 ` 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=025be707-a620-8e83-3aca-d962c5ff7ff4@tessares.net \
    --to=matthieu.baerts@tessares.net \
    --cc=geliang.tang@suse.com \
    --cc=mptcp@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.