From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] Squash to "selftests: bpf: verify ca_name of struct mptcp_sock"
Date: Mon, 2 May 2022 22:43:51 +0200 [thread overview]
Message-ID: <647deac5-ea7c-bfcf-e1cd-5ab91a3eee29@tessares.net> (raw)
In-Reply-To: <47419fbef3ed25bd1bb9d641e4817b85ea55ecda.1651329059.git.geliang.tang@suse.com>
Hi Geliang,
On 30/04/2022 16:31, Geliang Tang wrote:
> Read /proc/sys/net/ipv4/tcp_congestion_control directly, instead of
> using sysctl.
Thank you for the patch!
Now in our tree:
- 7578ba9005cf: "squashed" in "selftests: bpf: verify ca_name of struct
mptcp_sock"
- Results: 8ae619c5e009..929d7e14ecf1 (export)
Builds and tests are now in progress:
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20220502T203959
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
next prev parent reply other threads:[~2022-05-02 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 14:31 [PATCH mptcp-next] Squash to "selftests: bpf: verify ca_name of struct mptcp_sock" Geliang Tang
2022-04-30 16:14 ` Squash to "selftests: bpf: verify ca_name of struct mptcp_sock": Tests Results MPTCP CI
2022-05-02 20:43 ` Matthieu Baerts [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-07 6:17 [PATCH mptcp-next] Squash to "selftests: bpf: add MPTCP test base" Geliang Tang
2022-05-07 6:17 ` [PATCH mptcp-next] Squash to "selftests: bpf: verify ca_name of struct mptcp_sock" Geliang Tang
2022-03-13 11:48 Geliang Tang
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=647deac5-ea7c-bfcf-e1cd-5ab91a3eee29@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox