From: Mat Martineau <martineau@kernel.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 0/2] mptcp: Squash-to patches for "mptcp: more fixes for the in-kernel PM"
Date: Tue, 27 Aug 2024 13:09:42 -0700 (PDT) [thread overview]
Message-ID: <41e9e465-c8dd-fa13-a7d9-93a865f2159f@kernel.org> (raw)
In-Reply-To: <20240827-selftests-mptcp-longer-tests-v1-0-ec11c05fe980@kernel.org>
On Tue, 27 Aug 2024, Matthieu Baerts (NGI0) wrote:
> These two small squash-to patches would avoid issues recently seen on
> the Netdev CI when this series has been sent upstream.
>
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> ---
> Matthieu Baerts (NGI0) (2):
> Squash to "selftests: mptcp: join: check re-re-adding ID 0 endp"
> Squash to "selftests: mptcp: join: check re-re-adding ID 0 signal"
Hi Matthieu -
Both of these LGTM.
- Mat
>
> tools/testing/selftests/net/mptcp/mptcp_join.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> ---
> base-commit: a69c43e7eeeb5c959245dc2a20e6b41bc7afccb3
> change-id: 20240827-selftests-mptcp-longer-tests-f3b30918add9
>
> Best regards,
> --
> Matthieu Baerts (NGI0) <matttbe@kernel.org>
>
>
>
next prev parent reply other threads:[~2024-08-27 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 13:35 [PATCH mptcp-next 0/2] mptcp: Squash-to patches for "mptcp: more fixes for the in-kernel PM" Matthieu Baerts (NGI0)
2024-08-27 13:35 ` [PATCH mptcp-next 1/2] Squash to "selftests: mptcp: join: check re-re-adding ID 0 endp" Matthieu Baerts (NGI0)
2024-08-27 13:35 ` [PATCH mptcp-next 2/2] Squash to "selftests: mptcp: join: check re-re-adding ID 0 signal" Matthieu Baerts (NGI0)
2024-08-27 14:33 ` [PATCH mptcp-next 0/2] mptcp: Squash-to patches for "mptcp: more fixes for the in-kernel PM" MPTCP CI
2024-08-27 20:09 ` Mat Martineau [this message]
2024-08-28 6:37 ` Matthieu Baerts
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=41e9e465-c8dd-fa13-a7d9-93a865f2159f@kernel.org \
--to=martineau@kernel.org \
--cc=matttbe@kernel.org \
--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