netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dmitry Safonov via B4 Relay <devnull+0x7f454c46.gmail.com@kernel.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, shuah@kernel.org, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	0x7f454c46@gmail.com
Subject: Re: [PATCH net 0/4] selftests/net/tcp_ao: A bunch of fixes for TCP-AO selftests
Date: Tue, 16 Apr 2024 11:40:28 +0000	[thread overview]
Message-ID: <171326762899.16449.16473756279480443179.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240413-tcp-ao-selftests-fixes-v1-0-f9c41c96949d@gmail.com>

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Sat, 13 Apr 2024 02:42:51 +0100 you wrote:
> Started as addressing the flakiness issues in rst_ipv*, that affect
> netdev dashboard.
> 
> Signed-off-by: Dmitry Safonov <0x7f454c46@gmail.com>
> ---
> Dmitry Safonov (4):
>       selftests/tcp_ao: Make RST tests less flaky
>       selftests/tcp_ao: Zero-init tcp_ao_info_opt
>       selftests/tcp_ao: Fix fscanf() call for format-security
>       selftests/tcp_ao: Printing fixes to confirm with format-security
> 
> [...]

Here is the summary with links:
  - [net,1/4] selftests/tcp_ao: Make RST tests less flaky
    https://git.kernel.org/netdev/net/c/4225dfa4535f
  - [net,2/4] selftests/tcp_ao: Zero-init tcp_ao_info_opt
    https://git.kernel.org/netdev/net/c/b089b3bead53
  - [net,3/4] selftests/tcp_ao: Fix fscanf() call for format-security
    https://git.kernel.org/netdev/net/c/beb78cd1329d
  - [net,4/4] selftests/tcp_ao: Printing fixes to confirm with format-security
    https://git.kernel.org/netdev/net/c/b476c93654d7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2024-04-16 11:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-13  1:42 [PATCH net 0/4] selftests/net/tcp_ao: A bunch of fixes for TCP-AO selftests Dmitry Safonov via B4 Relay
2024-04-13  1:42 ` [PATCH net 1/4] selftests/tcp_ao: Make RST tests less flaky Dmitry Safonov via B4 Relay
2024-04-13  1:42 ` [PATCH net 2/4] selftests/tcp_ao: Zero-init tcp_ao_info_opt Dmitry Safonov via B4 Relay
2024-04-13  1:42 ` [PATCH net 3/4] selftests/tcp_ao: Fix fscanf() call for format-security Dmitry Safonov via B4 Relay
2024-04-13  1:50   ` Dmitry Safonov
2024-04-13  1:42 ` [PATCH net 4/4] selftests/tcp_ao: Printing fixes to confirm with format-security Dmitry Safonov via B4 Relay
2024-04-13  1:50   ` Dmitry Safonov
2024-04-16 11:40 ` patchwork-bot+netdevbpf [this message]
2024-04-16 14:28 ` [PATCH net 0/4] selftests/net/tcp_ao: A bunch of fixes for TCP-AO selftests Jakub Kicinski
2024-04-17 18:47   ` Dmitry Safonov
2024-04-17 20:46     ` Jakub Kicinski
2024-04-17 21:28       ` Jakub Kicinski
2024-04-17 22:30         ` Dmitry Safonov

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=171326762899.16449.16473756279480443179.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=0x7f454c46@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devnull+0x7f454c46.gmail.com@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).