From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, geliang@kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, horms@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, tanggeliang@kylinos.cn,
stable@vger.kernel.org
Subject: Re: [PATCH net 0/2] selftests: mptcp: fixes for diag.sh
Date: Mon, 04 Mar 2024 13:10:27 +0000 [thread overview]
Message-ID: <170955782703.9155.1922263393925918208.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240301-upstream-net-20240301-selftests-mptcp-diag-exit-timeout-v1-0-07cb2fa15c06@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 01 Mar 2024 18:11:21 +0100 you wrote:
> Here are two patches fixing issues in MPTCP diag.sh kselftest:
>
> - Patch 1 makes sure the exit code is '1' in case of error, and not the
> test ID, not to return an exit code that would be wrongly interpreted
> by the ksefltests framework, e.g. '4' means 'skip'.
>
> - Patch 2 avoids waiting for unnecessary conditions, which can cause
> timeouts in some very slow environments.
>
> [...]
Here is the summary with links:
- [net,1/2] selftests: mptcp: diag: return KSFT_FAIL not test_cnt
https://git.kernel.org/netdev/net/c/45bcc0346561
- [net,2/2] selftests: mptcp: diag: avoid extra waiting
https://git.kernel.org/netdev/net/c/f05d2283d111
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-04 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 17:11 [PATCH net 0/2] selftests: mptcp: fixes for diag.sh Matthieu Baerts (NGI0)
2024-03-01 17:11 ` [PATCH net 1/2] selftests: mptcp: diag: return KSFT_FAIL not test_cnt Matthieu Baerts (NGI0)
2024-03-01 17:11 ` [PATCH net 2/2] selftests: mptcp: diag: avoid extra waiting Matthieu Baerts (NGI0)
2024-03-04 13:10 ` patchwork-bot+netdevbpf [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=170955782703.9155.1922263393925918208.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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 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.