From: patchwork-bot+netdevbpf@kernel.org
To: Dmitry Safonov <dima@arista.com>
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, liuhangbin@gmail.com
Subject: Re: [PATCH net-next 0/2] selftest/net: Some more TCP-AO selftest post-merge fixups
Date: Tue, 02 Jan 2024 13:30:28 +0000 [thread overview]
Message-ID: <170420222841.17440.2782571129678540998.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231222-selftests-tcp-ao-fixups-v1-0-39c73817c372@arista.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 22 Dec 2023 01:59:05 +0000 you wrote:
> Note that there's another post-merge fix for TCP-AO selftests, but that
> doesn't conflict with these, so I don't resend that:
>
> https://lore.kernel.org/all/20231219-b4-tcp-ao-selftests-out-of-tree-v1-1-0fff92d26eac@arista.com/T/#u
>
> Signed-off-by: Dmitry Safonov <dima@arista.com>
>
> [...]
Here is the summary with links:
- [net-next,1/2] selftest/tcp-ao: Set routes in a proper VRF table id
https://git.kernel.org/netdev/net-next/c/72cd9f8d5a99
- [net-next,2/2] selftest/tcp-ao: Work on namespace-ified sysctl_optmem_max
https://git.kernel.org/netdev/net-next/c/80057b2080a8
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-01-02 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 1:59 [PATCH net-next 0/2] selftest/net: Some more TCP-AO selftest post-merge fixups Dmitry Safonov
2023-12-22 1:59 ` [PATCH net-next 1/2] selftest/tcp-ao: Set routes in a proper VRF table id Dmitry Safonov
2023-12-22 1:59 ` [PATCH net-next 2/2] selftest/tcp-ao: Work on namespace-ified sysctl_optmem_max Dmitry Safonov
2023-12-22 6:54 ` [PATCH net-next 0/2] selftest/net: Some more TCP-AO selftest post-merge fixups Hangbin Liu
2024-01-02 13:30 ` 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=170420222841.17440.2782571129678540998.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=davem@davemloft.net \
--cc=dima@arista.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--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