From: Matthieu Baerts <matttbe@kernel.org>
To: mptcp@lists.linux.dev, Geliang Tang <geliang@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH mptcp-net 0/2] mptcp: remove unneeded lock when listing scheds
Date: Sat, 19 Oct 2024 13:53:23 +0200 [thread overview]
Message-ID: <908ec9db-8397-4b44-a175-c9033f60b05b@kernel.org> (raw)
In-Reply-To: <20241017-mptcp-sched-avail-lock-v1-0-028ef592c6f4@kernel.org>
Hi Geliang,
On 17/10/2024 12:16, Matthieu Baerts (NGI0) wrote:
> A fix suggested by Paolo, and a small addition in the selftests to
> increase the code coverage. I guess they can both go to -net.
Thank you for your review on patch 1/2, I just applied the series in our
tree:
New patches for t/upstream-net and t/upstream:
- 7c2d2c795bd4: mptcp: remove unneeded lock when listing scheds
- 5f07b4f41bdd: selftests: mptcp: list sysctl data
- Results: e7969542d0a3..30a6ded06481 (export-net)
- Results: dc99b2bc6131..54b01fd36ac6 (export)
Tests are now in progress:
- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/136da0312931deb877b993a5d5a0fa6861e5da54/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/8d5658f1131d99357c5533d88541880bd97d0539/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-10-19 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 10:16 [PATCH mptcp-net 0/2] mptcp: remove unneeded lock when listing scheds Matthieu Baerts (NGI0)
2024-10-17 10:16 ` [PATCH mptcp-net 1/2] " Matthieu Baerts (NGI0)
2024-10-18 1:07 ` Geliang Tang
2024-10-17 10:16 ` [PATCH mptcp-net 2/2] selftests: mptcp: list sysctl data Matthieu Baerts (NGI0)
2024-10-17 11:22 ` [PATCH mptcp-net 0/2] mptcp: remove unneeded lock when listing scheds MPTCP CI
2024-10-19 11: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=908ec9db-8397-4b44-a175-c9033f60b05b@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
/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